Planner
List the services to cover
Returns the staff and fleet services of a date window, with who covers them and which resources are needed.
planner:readplanner:read- 120/min
- Server annotation: Read-only
- Server annotation: Idempotent
Result
generated from the schema
It returns ROWS, not services: each service comes as one summary row (rowKind: summary, with staffMemberId and vehicleId always null) and one detail row per person or vehicle assigned to it, all sharing the same orderServiceId. Group by orderServiceId: a service is uncovered when it only has its summary row, and covered when it has detail rows with an assignee, so a null on the summary row does not mean "uncovered". Internal services (not tied to an order) come with orderId and orderNumber empty and a serviceId that starts with is_. The identifier used to assign is orderServiceId.
Arguments
Window start, in ISO 8601 with offset.
Window end, in ISO 8601 with offset.
Which services to fetch. Defaults to both.
Available options: crew, fleet, both
Filter by status of the order they are attached to.
Available options: draft, reserved, all
Limit to one project.
Limits: min length 1, max length 100
Result
On success the result carries structuredContent with data and meta. These are the attributes of data.
Show the attributes of data
Service line identifier. It is the one passed when assigning.
Which row this is. A service comes as ONE summary row (the service itself, with staffMemberId and vehicleId always null) plus one detail row per person or vehicle assigned to it, all with the same orderServiceId. A service is covered when it has detail rows with an assignee, and uncovered when it only has the summary row.
Available options: summary, detail
Order the service is attached to; an empty string on internal services, which belong to no order.
Human-readable number of that order; an empty string on internal services.
Order status.
Customer of the order; null if not recorded.
Associated project; null if not applicable.
Project name; null if not applicable.
Catalogue service it comes from.
Service name.
Type: crew, fleet or general.
Assigned staff member. Only detail rows carry it; it is null on the summary row even when the service is covered.
Assigned vehicle. Only detail rows carry it; it is null on the summary row even when the service is covered.
Service start in ISO 8601 UTC.
Service end in ISO 8601 UTC.
Service line status.
How many units of the service are requested.
Linked schedule task; null if there is none.
Resources needed to cover it.
Show child attributesHide child attributes
What is needed: personnel or vehicle.
Available options: personnel, vehicle
How many are needed.
An error is a result with isError: true and the problem in content[0].; there is no structuredContent. See Errors.
The same operation by REST
This tool runs GET /api/v1/planner/services.
Related pages
Link to this section: Related pagesPlanner
List the services to cover
Returns the staff and fleet services of a date window, with who covers them and which resources are needed.
Guides
Safe writes
An assistant that can write can also write the wrong thing. Decide which tools need a person, retry without duplicating, and know what a write sets in motion.
Guides
Errors
A tool error is a result with
isError: trueand the problem in the first text block. Branch on itscode.
Was this page helpful?