Spoke Dispatch MCP server

Get a driver

get_driver

Read-only

Retrieve details for a single driver by ID, including name, active status, depots, and route overrides; optionally add contact info and addresses.

Instructions

One driver: name, active status, depots and route overrides. Email, phone and start/end address only with include_contact_details.

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": {
      "driver_id": "<driver_id>"
    },
    "name": "get_driver"
  }
}

Input Schema

Name	Required	Description	Default
`driver_id`	Yes	Driver ID (drivers/<id> or the bare <id>)
`include_contact_details`	No	Include the driver's email address, phone number and full start/end addresses

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one useful behavioral detail — that contact fields are gated behind include_contact_details — but says nothing about errors, permissions, or what happens with an unknown ID beyond what the schema implies.

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 tight sentences with zero filler; the returned-field list is front-loaded and the conditional-contact caveat follows naturally. Every clause carries information.

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 no output schema, the description correctly compensates by listing the returned fields, and the conditional contact-detail rule is stated. It stops short of describing error behavior or the driver_id format nuances, but it is sufficient for correct invocation.

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 both parameters are already documented, including the include_contact_details effect. The description restates that effect in different terms (email/phone/start-end address) without adding syntax or edge cases, so it earns the baseline 3 rather than more.

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 names the resource (a single driver) and enumerates the returned fields (name, active status, depots, route overrides), which implicitly distinguishes it from list_drivers and get_route. It lacks an explicit verb like 'retrieve', but the singular 'One driver' clearly signals a single-record fetch versus a listing.

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?

Usage is only implied: the singular framing suggests fetching one known driver rather than browsing, but no alternative (e.g., list_drivers for enumeration) is named and no precondition is stated. Adequate for a simple read but leaves routing to sibling tools to inference.

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

Deploy Server