STEADYWRK Field Service Dispatch

Create a dispatch work order

dispatch.order

Destructive

Create a field-service order and return its status URL. HTTP 201 returns a created order; HTTP 202 returns an order accepted_pending_fulfilment with fulfilled=false. Order creation requires a provisioned integration key through x-api-key. MCP also accepts that key through Authorization: Bearer; direct REST order creation requires x-api-key. A self-serve OAuth token authenticates but is not entitled to create orders: HTTP 402 payment_required (JSON-RPC -32002 over MCP). Anonymous callers receive HTTP 401 with WWW-Authenticate. Provisioning contact: hello@steadywrk.app.

Input Schema

TableJSON Schema

Name	Required	Default
`trade`	Yes
`urgency`	No	routine
`location`	Yes
`nte_cents`	No
`description`	Yes
`callback_url`	No
`reference_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "A recorded work order — fulfilled (contractor matched, HTTP 201) or accepted_pending_fulfilment (no contractor yet, HTTP 202) — or a business/entitlement error passthrough.",
+  "oneOf": [
+    {
+      "properties": {
+        "accepted": {
+          "const": true,
+          "type": "boolean"
+        },
+        "created": {
+          "const": true,
+          "type": "boolean"
+        },
+        "fulfilled": {
+          "type": "boolean"
+        },
+        "fulfilment": {
+          "description": "Present only when fulfilled=false.",
+          "properties": {
+            "assigned": {
+              "const": false,
+              "type": "boolean"
+            },
+            "detail": {
+              "type": "string"
+            },
+            "escalation_contact": {
+              "type": "string"
+            },
+            "reason": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "order": {
+          "additionalProperties": true,
+          "properties": {
+            "assigned_contractor_ref": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "created_at": {
+              "type": "string"
+            },
+            "estimated_response_minutes": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "id": {
+              "type": "string"
+            },
+            "location": {
+              "type": "object"
+            },
+            "quoted_cost_cents": {
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "quoted_cost_usd": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "status": {
+              "enum": [
+                "pending_dispatch",
+                "accepted_pending_fulfilment"
+              ],
+              "type": "string"
+            },
+            "trade": {
+              "type": "string"
+            },
+            "urgency": {
+              "enum": [
+                "emergency",
+                "urgent",
+                "routine",
+                "scheduled"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "status",
+            "trade",
+            "location",
+            "urgency",
+            "created_at"
+          ],
+          "type": "object"
+        },
+        "tracking": {
+          "properties": {
+            "auth": {
+              "type": "string"
+            },
+            "status_url": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "created",
+        "accepted",
+        "fulfilled",
+        "order",
+        "tracking"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": true,
+      "description": "Business/rate-limit/entitlement error passthrough.",
+      "properties": {
+        "error": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedJul 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description adds substantial behavioral detail: exact HTTP success codes and their meanings, the accepted_pending_fulfilment state, authentication mechanisms, OAuth entitlement limitations with HTTP 402, and anonymous caller behavior with HTTP 401. This is rich, non-obvious context that helps an agent anticipate side effects and errors.

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 dense but well-structured, with the core purpose front-loaded and each subsequent sentence covering a distinct and important aspect: response codes, authentication options, entitlement restrictions, failure modes, and support contact. There is no filler or repetition.

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 creation tool with complex authentication, entitlement, and response semantics, the description covers all critical aspects an agent needs to invoke it correctly: expected status codes, required auth context, OAuth limitations, failure responses, and a support contact. Since an output schema exists, detailed return-value documentation is not necessary here.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter meaning. It does not explain any of the seven parameters, such as nte_cents, callback_url, reference_id, or the nested location object. While the parameter names are somewhat self-explanatory and the schema provides types/defaults/enums, the description adds no semantic value beyond what the schema already shows.

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 opens with a specific verb and resource: 'Create a field-service order and return its status URL.' This clearly identifies the tool's action and differentiates it from sibling tools like dispatch.estimate and dispatch.quote, which are concerned with estimation and quoting rather than order creation.

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

Usage Guidelines4/5

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

The description gives clear operational guidance: HTTP 201 vs 202 outcomes, the need for a provisioned integration key via x-api-key, and the alternative Authorization: Bearer mechanism for MCP. It also explains that OAuth tokens are authenticated but not entitled to create orders. It does not explicitly name sibling alternatives for when not to use this tool, but the context of when to use it is strong.

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

All STEADYWRK Field Service Dispatch tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation4/5

dispatch.estimate, dispatch.quote, and dispatch.index all touch pricing, but their descriptions clearly distinguish public modeled estimates from credentialed quotes and reference catalog data. dispatch.order and dispatch.evals are distinct, while agentic.readiness_probe is unrelated but unambiguous.

Naming Consistency4/5

Most tools follow a consistent dispatch.<noun/verb> pattern with lowercase single-word names like dispatch.quote and dispatch.order. The agentic.readiness_probe tool breaks the pattern with a different prefix and underscore suffix, and dispatch.evals uses an abbreviation, but the overall convention remains readable and mostly predictable.

Tool Count4/5

Six tools is a reasonable, well-scoped count for a field-service dispatch server. However, agentic.readiness_probe appears to belong to a separate storefront-readiness product, which slightly dilutes the server's focus even though the count itself is not excessive.

Completeness3/5

The set covers public pricing estimates, quotes, reference data, methodology documentation, and order creation. It lacks order status, update, list, or cancel operations, and fulfillment is only represented by a returned status URL. That leaves a notable lifecycle gap for a server named Field Service Dispatch.

Resources

Need Help?