Skip to main content
Glama

Create work order schedule

create_work_order_schedule

Schedule a work order for a technician on a date (one entry of a day plan). stop_order gives the position in the technician's day; leave it unset for an unordered calendar entry. Requires work_order_schedules:write scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "work_order_id": "<work_order_id>",
      "technician_id": "<technician_id>",
      "scheduled_date": "<scheduled_date>"
    },
    "name": "create_work_order_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
stop_orderNo1-based stop position in the day plan
technician_idYesTechnician Clerk user ID (required) - resolve via list_users
work_order_idYesWork order ID (required) - resolve via list_work_orders
scheduled_dateYesDate (YYYY-MM-DD, required)
duration_minutesNoPlanned duration in minutes
scheduling_notesNoScheduling notes
scheduled_end_timeNoEnd time (HH:MM)
travel_time_minutesNoTravel time from previous stop
scheduled_start_timeNoStart time (HH:MM)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / technician_id / description
      Previous value: -"Technician Clerk user ID (required)"New value: +"Technician Clerk user ID (required) - resolve via list_users"
    • changedInput schema / properties / work_order_id / description
      Previous value: -"Work order ID (required)"New value: +"Work order ID (required) - resolve via list_work_orders"
  2. Changed9 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / duration_minutes / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / duration_minutes / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / stop_order / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / stop_order / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / travel_time_minutes / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / travel_time_minutes / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / work_order_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  3. Changed9 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / duration_minutes / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / duration_minutes / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / stop_order / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / stop_order / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / travel_time_minutes / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / travel_time_minutes / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / work_order_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed9 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / duration_minutes / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / duration_minutes / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / stop_order / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / stop_order / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / travel_time_minutes / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / travel_time_minutes / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / work_order_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only establish the generic profile (readOnly=false, destructive=false, idempotent=false, closed-world); the description adds the concrete auth requirement (work_order_schedules:write scope), which is exactly the kind of context annotations cannot convey. It stops short of disclosing conflict/overlap handling or duplicate-creation consequences, which matter given idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, zero padding, and the core purpose is front-loaded ahead of the optional-parameter nuance and the scope requirement. Every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter create tool with a fully documented schema, no output schema, and annotations covering the safety profile, the description covers the essentials: what it creates, how the key optional field behaves, and what permission is needed. Remaining unknowns (conflict handling, return payload) are either out of scope or absent from the tool contract itself.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already explains all nine parameters and the baseline is 3. The description still earns credit by explaining the unset case for stop_order — that omitting it produces an unordered calendar entry — which the schema's '1-based stop position in the day plan' does not state. It adds nothing about the time/duration fields, but those are fully documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — scheduling a work order for a technician on a date — and the parenthetical 'one entry of a day plan' clarifies that this creates a schedule entry, not the work order itself, which separates it from create_work_order. It does not name or contrast any sibling directly, so an agent still has to infer that update_work_order_schedule and list_work_order_schedules are the other paths.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence about leaving stop_order unset for an unordered calendar entry is genuine usage guidance, and the write-scope requirement is a useful precondition. However, there is no when-not guidance, no mention of alternatives such as create_work_order or update_work_order_schedule, and no indication of behavior when a technician is already booked at that time.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources