MyGeotab MCP

Start here for any MyGeotab task: get authoritative guidance on how to use the MyGeotab APIs effectively. Call GetSkill BEFORE composing MyGeotab queries for a task, passing the user's question or intent. It returns vetted, task-specific instructions — which entity and method to use, how search filters nest, how to scope fromDate/toDate, when to paginate — so your subsequent Get/GetCountOf/ Add/Set calls are correct and efficient. This prevents the most common MyGeotab mistakes; do not rely on prior assumptions about the API.

GetSkill

Get entity type schema (field names, types, required/optional). No database auth needed. Call before Add/Set to discover required fields. Ref: https://developers.geotab.com/myGeotab/apiReference/objects/

GetEntity

Get posted road speed limits along a device's travel path within a date range. Ref: https://developers.geotab.com/myGeotab/apiReference/methods/GetPostedRoadSpeedsForDevice/

GetPostedRoadSpeedsForDevice

Get device status, connectivity, and health information for Go Focus cameras. This tool is for Go Focus cameras only. It returns deviceStatus, lastConnectedAt, lastRecordingUpdatedAt, lastRecordingHealth, and deviceModel for each device. Examples: - Get info for multiple devices: goFocusDeviceIds=['device1', 'device2'], database='g560' - Check single device: goFocusDeviceIds=['device1'], database='my_fleet' Returns device information as JSON with fields: - deviceStatus: Current device status (string) - lastConnectedAt: ISO timestamp or null - lastRecordingUpdatedAt: ISO timestamp or null - lastRecordingHealth: Health indicator string or null - deviceModel: Device model string or null

GetDevicesInformation

Get all available HOS rule sets with ID and name for driver working hours regulations.

GetHosRuleSets

List all supported entity types for Get, Add, Set, and Remove operations. Only writable entity types allowed for Add/Set/Remove. Ref: https://developers.geotab.com/myGeotab/apiReference/objects/ Call this tool first if you are unsure which typeName to pass to Get, Add, Set, or Remove.

ListEntities

Modify an existing entity. Entity 'id' required; include only fields to change — omitted fields unchanged. Examples: typeName='Device',entity={id:'b1',name:'New Name'} | typeName='User',entity={id:'b2',isDriver:true}. Ref: https://developers.geotab.com/myGeotab/apiReference/methods/Set/

Set

Ask Geotab Ace AI to generate fleet insights via natural language. Ace generates SQL, executes queries, returns results with reasoning. Pass new_chat=true to start; use chat_id to continue conversation.

GetAceResults

Retrieve entities by type. Paginate via fromDate/toDate narrowing — not page numbers. Use GetCountOf to pre-check size. Examples: search={id:'b1'} | search={name:'%truck%'} | search={fromDate:'2024-01-01T00:00:00Z',toDate:'2024-01-02T00:00:00Z'} | search={deviceSearch:{id:'b1'},fromDate:'...',toDate:'...'} | propertySelector={fields:['id','name']} | resultsLimit=100. Ref: https://developers.geotab.com/myGeotab/apiReference/methods/Get/ ## Result Size — IMPORTANT Always specify resultsLimit. Omitting it returns ALL entities and may overflow context. Recommended values: - Exploration / single device lookup: 10–25 - Investigations: 100–500 - Bulk operations: 1000–10000 (always use propertySelector with large limits) ## Field Selection Use propertySelector to reduce response size by up to 80%: propertySelector={"fields": ["id", "name", "serialNumber"]} This is critical for entities with many fields (Device, User, Trip). ## Common Mistake The 'search' parameter must contain nested criteria — do NOT pass search fields at the top level: - Correct: search={"id": "b123"} - Wrong: id="b123" — 'id' must be inside 'search', not a top-level parameter - Correct: search={"name": "Fleet Vehicle"} - Wrong: name="Fleet Vehicle" — same mistake If the entity type is unknown, call ListEntities first to see all supported types.

Get

Search video/snapshot media requests. Always provide time range. Examples: requestStartTime='2024-01-01T00:00:00.000Z',requestEndTime='2024-01-02T00:00:00.000Z',statuses=['MediaAvailable'] | goDeviceIds=['b1'],resourceType=['Video'] | ruleIds=['ruleId'],types=['Exception']. Pass result's mediaRequestId to GetMediaUrl for playback. Paginate: increment resultsPage by 1.

SearchMedia

Record user feedback about the MyGeotab MCP server — its tools, or the accuracy of an answer — for product improvement. WHEN TO CALL: (a) the user explicitly asks to leave feedback, report a problem, or praise something; OR (b) a tool has failed repeatedly and the user appears blocked. For case (b), FIRST summarize the issue and show the user exactly what you would submit, and call this tool ONLY after they confirm. Do not offer to leave feedback more than once per session unless the user brings it up. AUTHORSHIP & CONFIRMATION: if feedback_text is the user's own words verbatim, set source='user_explicit'. If you wrote OR enriched any of it — including folding in an AI-summarized context (what the user was doing, expected, and where it broke) — set source='ai_on_behalf' and you MUST show the user the exact final text and get their explicit confirmation before calling this tool. Never submit AI-composed text the user hasn't seen and approved. Keep any context about the interaction, not raw customer records. This is product-improvement signal collected internally — it is NOT a support ticket and does not open a case or guarantee a response; say so if the user expects a reply. Put the full feedback in feedback_text, set sentiment ('positive'/'negative') and source, and pass the database the user was working in when you know it.

SubmitFeedback

Store file content for a MediaFile entity. Requires base64-encoded data. Ref: https://developers.geotab.com/myGeotab/apiReference/methods/UploadMediaFile/

UploadMediaFile