Skip to main content
Glama

Update work order schedule

update_work_order_schedule
DestructiveIdempotent

Update a work order schedule entry by ID (date, times, stop_order, notes). work_order_id is immutable. 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": {
      "id": "<id>"
    },
    "name": "update_work_order_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWork order schedule ID
stop_orderNo1-based stop position in the day plan
technician_idNoTechnician Clerk user ID - resolve via list_users
scheduled_dateNoDate (YYYY-MM-DD)
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. Changed1 schema field changed
    • changedInput schema / properties / technician_id / description
      Previous value: -"Technician Clerk user ID"New value: +"Technician Clerk user ID - resolve via list_users"
  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 / 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})$"
    • 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
  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 / 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})$"
    • 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
  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 / 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})$"
    • 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
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already disclose readOnly=false, destructive=true, idempotent=true, and openWorld=false. The description adds useful context by stating the required work_order_schedules:write scope and that work_order_id is immutable, but it does not explain partial-update behavior or what happens to omitted fields, which is important for a destructive update.

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?

The description is front-loaded, compact, and free of filler. Every fragment contributes useful information about the operation, immutability constraint, and authorization requirement.

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

Completeness4/5

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

Given full schema coverage and rich annotations, the description provides the key operational context an agent needs: update by ID, required scope, and immutable field. It still omits partial-update semantics and return behavior, but those gaps are moderate rather than disqualifying for a tool whose parameters and safety profile are otherwise well documented.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all nine parameters including formats and meanings. The description lists only a subset of updatable fields (date, times, stop_order, notes) and adds little parameter-level meaning beyond noting work_order_id immutability.

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

Purpose5/5

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

The description states a specific verb and resource: "Update a work order schedule entry by ID," and lists the fields being changed. This clearly distinguishes it from create/get/list/delete work order schedule siblings and from update_work_order.

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?

It implies usage by saying the entry is updated by ID and notes the required write scope, plus an immutable field. However, it does not explicitly route the agent to alternatives such as create_work_order_schedule for new entries or list_work_order_schedules to resolve the ID.

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