STEADYWRK Field Service Dispatch

Estimate dispatch cost

dispatch.estimate

Read-onlyIdempotent

Public modeled field-service price estimate using cited BLS wage data and disclosed model assumptions. Returns wage_basis and billed_estimate so callers can inspect the calculation and geographic basis. The response identifies estimates based on a national baseline and distinguishes model assumptions from observed prices. Use dispatch.quote with an accepted credential to request a quote. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`trade`	Yes	Trade code (plumbing, electrical, HVAC, etc.)
`urgency`	No		routine
`location`	Yes

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 full wage-to-billed-rate estimate, or an unknown/missing trade error — never a fabricated number.",
+  "oneOf": [
+    {
+      "properties": {
+        "basis": {
+          "const": "wage_to_billed_rate_transform",
+          "type": "string"
+        },
+        "billed_estimate": {
+          "additionalProperties": true,
+          "description": "What a buyer pays — every component of the arithmetic, re-derivable via formula.",
+          "properties": {
+            "billed_hourly_rate_cents": {
+              "type": "integer"
+            },
+            "billed_hourly_rate_routine_cents": {
+              "type": "integer"
+            },
+            "currency": {
+              "const": "USD",
+              "type": "string"
+            },
+            "formula": {
+              "type": "string"
+            },
+            "labor_burden_multiplier": {
+              "type": "number"
+            },
+            "minimum_billable_hours": {
+              "type": "number"
+            },
+            "total_cents": {
+              "type": "integer"
+            },
+            "total_usd": {
+              "type": "number"
+            },
+            "trip_fee_cents": {
+              "type": "integer"
+            },
+            "urgency_multiplier": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "disclosure": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "estimated": {
+          "const": true,
+          "type": "boolean"
+        },
+        "estimated_cost_cents": {
+          "description": "Alias of billed_estimate.total_cents.",
+          "type": "integer"
+        },
+        "location_resolution": {
+          "additionalProperties": true,
+          "properties": {
+            "location_sensitive": {
+              "type": "boolean"
+            },
+            "reason": {
+              "type": "string"
+            },
+            "resolved_metro": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "resolved_metro_label": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "scope": {
+              "enum": [
+                "metro_cited",
+                "national_baseline",
+                "mena_coverage_beta"
+              ],
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "rate_card": {
+          "properties": {
+            "median_dollars": {
+              "type": "number"
+            },
+            "p25_dollars": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "p75_dollars": {
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        "rate_model_version": {
+          "type": "string"
+        },
+        "source": {
+          "const": "public_rate_card",
+          "type": "string"
+        },
+        "trade": {
+          "type": "string"
+        },
+        "urgency": {
+          "enum": [
+            "emergency",
+            "urgent",
+            "routine",
+            "scheduled"
+          ],
+          "type": "string"
+        },
+        "wage_basis": {
+          "additionalProperties": true,
+          "description": "The cited hourly WAGE input — NOT the price.",
+          "properties": {
+            "bls_occ_code": {
+              "type": "string"
+            },
+            "kind": {
+              "const": "hourly_wage",
+              "type": "string"
+            },
+            "median_cents": {
+              "type": "integer"
+            },
+            "note": {
+              "type": "string"
+            },
+            "p25_cents": {
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "p75_cents": {
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "scope_label": {
+              "type": "string"
+            },
+            "source_url": {
+              "type": "string"
+            },
+            "trade_label": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "estimated",
+        "source",
+        "basis",
+        "rate_model_version",
+        "trade",
+        "urgency",
+        "location_resolution",
+        "wage_basis",
+        "billed_estimate",
+        "estimated_cost_cents",
+        "rate_card",
+        "disclosure"
+      ],
+      "type": "object"
+    },
+    {
+      "description": "Trade was missing or not recognized. No number is fabricated.",
+      "properties": {
+        "error": {
+          "enum": [
+            "unknown_trade",
+            "trade_required"
+          ],
+          "type": "string"
+        },
+        "estimated": {
+          "const": false,
+          "type": "boolean"
+        },
+        "known_trades": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "source": {
+          "const": "public_rate_card",
+          "type": "string"
+        },
+        "trade": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "valid_trades": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "estimated",
+        "source",
+        "error",
+        "trade",
+        "valid_trades",
+        "known_trades"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

AddedAug 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior, so the description adds value by disclosing that this is a modeled estimate using cited BLS wage data, that responses distinguish model assumptions from observed prices, and that a national baseline is used. This goes beyond annotation hints without contradicting them.

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 with the core purpose and data source, then explains the return fields, then the model vs. observed distinction, and finally the quote alternative. Every sentence carries distinct information with no redundancy.

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?

With an output schema present and annotations covering safety, the description supplies the missing context: public access, no API key, cited data source, returns for inspection, and the route to get a real quote. It is slightly light on how parameters like urgency affect the estimate, but the schema and output schema cover much of the remaining needed detail.

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 33%, so the description should compensate for undocumented parameters, but it does not. It mentions 'geographic basis' and a 'national baseline,' which loosely relates to location, but it provides no meaningful guidance on trade, urgency, or location semantics beyond the schema's terseness.

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 uses a specific verb and resource: 'field-service price estimate' with a clear modeled/observed distinction. It also differentiates from the sibling tool by explicitly saying quote requests belong to dispatch.quote, so an agent can immediately tell this tool apart.

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 explicitly points to dispatch.quote with an accepted credential for requesting a quote, which clarifies the main alternative. It also states that no API key is required, giving a clear access condition. It does not enumerate all sibling tools, but the key decision boundary is provided.

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?