Spoke Dispatch MCP server

List operations

list_operations

Read-only

Check long-running dispatch operations to see if plan optimization is done or running, who started it, the target plan, and whether stops were optimized, skipped, or failed.

Instructions

Long-running operations (currently only plan_optimization) with whether they are done, who started them, the target plan and the result (stops optimized, stops skipped with reasons, or an error).

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_operations"
  }
}

Input Schema

Name	Required	Description
`done`	No	Only finished (true) or only running (false) operations (the API's filter.done)
`type`	No	Only operations of this type (the API's filter.type)
`page_token`	No	next_page_token from a previous call, to continue the same list
`max_results`	No	Minimum number of records to return; whole pages are returned, so a few more may come back

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

B3.2/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 useful context about result shape (stops optimized, stops skipped with reasons, or an error), but says nothing about pagination behavior despite page_token/max_results existing, nor about result limits.

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

Conciseness4/5

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

A single dense sentence that front-loads the resource and then the returned fields. Efficient with no wasted preamble, though the parenthetical list is slightly run-on.

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 carries the return-value burden and does describe the result contents (optimized/skipped counts, errors). Combined with a fully documented schema, this is largely complete; only pagination/continuation behavior is left unstated.

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 four parameters (done, type, page_token, max_results) are already documented in the schema with API filter mappings. The description adds no additional parameter semantics beyond noting the single valid operation type, making the baseline 3 appropriate.

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?

States a specific resource (long-running operations) and enumerates the payload (done status, starter, target plan, result), so an agent knows what it retrieves. It does not differentiate itself from the get_operation sibling, which covers the same domain, so it stops short of a 5.

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

Usage Guidelines2/5

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

No when-to-use guidance and no mention of the alternative get_operation for fetching a single operation. The agent must infer that this is the bulk/list counterpart, and nothing tells it when listing is preferable.

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

Deploy Server