Skip to main content
Glama

STEADYWRK Field Service Dispatch

by app.steadywrk

Get a dispatch quote

dispatch.quote

Request a field-service quote by trade, location, and urgency. Returns availability and quote details when available. Accepts a provisioned integration key through x-api-key or a scoped self-serve OAuth token through Authorization: Bearer. MCP also accepts the provisioned key through Authorization: Bearer. Obtain a self-serve token through POST /api/mcp/oauth/register, then POST /api/mcp/oauth/token with grant_type=client_credentials. Anonymous callers receive HTTP 401 with WWW-Authenticate. Public modeled pricing is available through dispatch.estimate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tradeYesTrade code (plumbing, electrical, HVAC, etc.)
urgencyNoroutine
locationYes
nte_centsNo
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "A matched-contractor quote, a no-availability response, or a business/auth error passthrough from the downstream dispatch API.",
+  "oneOf": [
+    {
+      "description": "A contractor was matched.",
+      "properties": {
+        "available": {
+          "const": true,
+          "type": "boolean"
+        },
+        "next_steps": {
+          "properties": {
+            "contact": {
+              "type": "string"
+            },
+            "dispatch": {
+              "type": "string"
+            },
+            "docs": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "quote": {
+          "properties": {
+            "alternates_count": {
+              "type": "integer"
+            },
+            "best_match": {
+              "properties": {
+                "estimated_cost_cents": {
+                  "type": "integer"
+                },
+                "estimated_cost_usd": {
+                  "type": "string"
+                },
+                "estimated_response_minutes": {
+                  "type": "number"
+                },
+                "match_score": {
+                  "type": "number"
+                }
+              },
+              "type": "object"
+            },
+            "estimated_eta": {
+              "type": "string"
+            },
+            "generated_at": {
+              "type": "string"
+            },
+            "location": {
+              "type": "object"
+            },
+            "trade": {
+              "type": "string"
+            },
+            "urgency": {
+              "enum": [
+                "emergency",
+                "urgent",
+                "routine",
+                "scheduled"
+              ],
+              "type": "string"
+            },
+            "valid_for_minutes": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "trade",
+            "location",
+            "urgency",
+            "estimated_eta",
+            "best_match",
+            "alternates_count",
+            "generated_at",
+            "valid_for_minutes"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "available",
+        "quote",
+        "next_steps"
+      ],
+      "type": "object"
+    },
+    {
+      "description": "No contractor is currently available for this trade/location.",
+      "properties": {
+        "available": {
+          "const": false,
+          "type": "boolean"
+        },
+        "location": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "trade": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "available",
+        "message",
+        "trade",
+        "location"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": true,
+      "description": "Business/rate-limit/auth error passthrough.",
+      "properties": {
+        "error": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already indicate the tool is not read-only and not idempotent. The description adds useful behavioral context about authentication methods, the 401 response for anonymous callers, and token acquisition endpoints. It does not disclose other side effects, such as whether requesting a quote creates records, expires, or commits to anything.

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

Conciseness3/5

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

The description is front-loaded with purpose and keeps the core request semantics in the first sentence. The authentication section is somewhat redundant and verbose, especially the 'MCP also accepts the provisioned key through Authorization: Bearer' sentence, which repeats information already implied by the prior sentence.

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

Completeness3/5

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

The description covers authentication thoroughly, including token endpoints and anonymous 401 behavior, and it points to a sibling for modeled pricing. However, it does not explain the role of nte_cents and description, nor does it clarify what happens when availability and quote details are not available. An output schema may cover return shape, but invocation-level completeness is only adequate.

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 only 20%, so the description carries a heavier burden for explaining parameters. It mentions trade, location, and urgency, but it does not explain the meaning of nte_cents, description, or the nested location object's constraints beyond what the schema already shows. The cryptic nte_cents parameter is left undocumented, which is a meaningful usability gap.

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: 'Request a field-service quote by trade, location, and urgency.' It also distinguishes itself from dispatch.estimate by noting 'Public modeled pricing is available through dispatch.estimate,' which helps separate the two sibling tools. However, the exact boundary between a quote and an estimate remains somewhat implicit rather than explicitly defined.

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 gives clear context that authorization is required and mentions dispatch.estimate as an alternative for 'public modeled pricing.' It does not, however, explicitly state when to prefer dispatch.quote over dispatch.estimate or dispatch.order, nor does it explain the workflow between quote, estimate, and order.

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 toolsInspect
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