OMD Go Tools
The OMD Go tool group gives the agent read and write access to your OMD Go workforce management data via the OData API.
Available tools
| Tool | Description |
|---|---|
get_odata_schema |
Retrieve the schema for one or more OData entities. Must be called before querying an entity. |
get_odata_entity |
Query an OData entity with a filter, select, expand, or orderby expression. |
create_odata_entity |
Create a new entity (e.g. a task or customer). Requires confirmation. |
update_odata_entity |
Update fields on an existing entity. Requires confirmation. |
delete_odata_entity |
Delete an entity. Requires confirmation. |
replan_task |
Trigger replanning for a specific task and return the available options. |
Supported entities
The following OData entities are accessible:
| Entity | Description |
|---|---|
Task |
Service tasks assigned to workers |
Trip |
A worker's daily trip (collection of visits) |
Customer |
Customer accounts |
Resource |
Mobile workers / field resources |
ResourceGroup |
Groups of resources (territories) |
Territory |
Geographical planning areas |
ContractType |
Contract type definitions |
ContractLine |
Individual contract line items |
Contract |
Customer service contracts |
Status |
Task and trip status values |
AttachmentType |
Types of task attachments |
SubType |
Task subtypes |
TaskAttachment |
Attachments linked to tasks |
Query syntax
The tools use the standard OData query syntax:
$filter— filter results (e.g.$filter=Territory/name eq 'Neuss')$select— choose specific fields (e.g.$select=id,name,scheduled)$expand— include related entities inline (e.g.$expand=Territory)$orderby— sort results (e.g.$orderby=scheduled asc)$top/$skip— pagination
Date/time values must use the OData DateTimeOffset format:
scheduled gt 2025-01-01T16:00:00.000Z
The config_id (OMD instance) is injected automatically — do not include it in the query string.
Example interactions
User: "Show me all tasks in the Düsseldorf territory for next Monday."
The agent:
1. Calls get_odata_schema for Task and Territory.
2. Calls get_odata_entity with $filter=Territory/name eq 'Düsseldorf' and scheduled ge 2025-07-28T00:00:00.000Z and scheduled lt 2025-07-29T00:00:00.000Z&$expand=Customer,Territory.
3. Presents the results in a readable table.
User: "Update the estimated duration of task TK-12345 to 90 minutes."
The agent:
1. Calls get_odata_entity to confirm the task exists.
2. Proposes calling update_odata_entity and requests user confirmation.
3. On approval, executes the update.