Skip to main content
Glama

List work orders

list_work_orders
Read-onlyIdempotent

List work orders. Filter by status (NEW, IN_PROGRESS, ON_HOLD, COMPLETED, CANCELLED), priority (LOW, MEDIUM, HIGH, URGENT), type (PM, REACTIVE), and site. Amounts are bare numbers with no currency: call get_organization_settings for currency_code before stating one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_work_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: all pages fetched automatically)
typeNoFilter by type: PM (preventive) or REACTIVE
searchNoSearch by name
statusNoFilter by status: NEW, IN_PROGRESS, ON_HOLD, COMPLETED, CANCELLED
site_idNoFilter by site ID - resolve via list_sites
per_pageNoItems per page (default: 1000, max: 1000). All pages are fetched automatically.
priorityNoFilter by priority: LOW, MEDIUM, HIGH, URGENT

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site_id / description
      Previous value: -"Filter by site ID"New value: +"Filter by site ID - resolve via list_sites"
  2. Changed2 schema fields changed
    • changedInput schema / properties / priority / description
      Previous value: -"Filter by priority: LOW, MEDIUM, HIGH, CRITICAL"New value: +"Filter by priority: LOW, MEDIUM, HIGH, URGENT"
    • changedInput schema / properties / type / description
      Previous value: -"Filter by type: CORRECTIVE, PREVENTIVE, EMERGENCY, INSPECTION"New value: +"Filter by type: PM (preventive) or REACTIVE"
  3. Changed4 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 / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_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})$"
  4. Changed4 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 / page / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / site_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})$"
  5. Changed4 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 / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_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})$"
  6. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds valuable behavioral context not in annotations: it warns that amounts are bare numbers and instructs the agent to call get_organization_settings for the currency code before stating one. This is a meaningful caveat for interpreting output.

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?

Two tightly written sentences, front-loaded with the core action and then the filter options and a critical output-handling note. No wasted words or redundancy that isn't justified by the schema's enum values being surfaced at a glance.

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?

For a list tool with no output schema and complete parameter descriptions, the definition is nearly complete: it covers the available filters and a non-obvious currency caveat. It omits mention of search, pagination, or the relationship to similar tools, but those are either schema-documented or minor for a read-only listing operation.

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 description coverage is 100%, so all parameters are already documented in the input schema. The description repeats the filterable values for status, priority, type, and site, which adds no new semantic detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description states a specific verb and resource ('List work orders'), making the tool's core purpose immediately clear. However, it does not differentiate this tool from its sibling list_work_requests or get_work_order, which could be relevant for an agent deciding between them.

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 description implies usage by listing filter dimensions, but it never states when to use this tool versus alternatives (e.g., get_work_order for a single record, list_work_requests for requests). No exclusions or prerequisites are given.

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