Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

Simulate delivery progress

simulate_delivery_progress

Advance a mock delivery to a later stage or reject it with a reason to test the full delivery lifecycle in a sandbox.

Instructions

Testing only (mock/sandbox): move a simulated delivery to a later stage, or reject it with a reason, to demo the full lifecycle.

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": {
      "delivery_id": "<delivery_id>",
      "target_stage": "<target_stage>"
    },
    "name": "simulate_delivery_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYesDelivery id returned by dispatch_robot
target_stageYes
reject_reasonNoRequired when target_stage is 'rejected'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare a non-read-only mutation (readOnlyHint=false, destructiveHint=false), and the description usefully adds that the effects are confined to a mock/sandbox environment — context the annotations do not convey. However, it omits whether stages must progress sequentially, whether backward transitions are rejected, whether the delivery must be in a simulated state, and what happens on an invalid transition, all of which matter for a state-machine tool.

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 sentence with the most decision-relevant qualifier ('Testing only (mock/sandbox)') front-loaded, and no restatement of parameter names. It is efficient, though the brevity is achieved partly by leaving transition rules unstated.

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?

For a three-parameter state-machine tool with no output schema, the definition covers what the tool does and where it is safe to use, but leaves the transition semantics and return behavior unexplained. An agent knows roughly what to call and when, but not what a valid call sequence looks like.

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 67% with descriptions on delivery_id and reject_reason, so the schema does most of the work. The description adds only the forward-only connotation of 'later stage' and the reject-with-reason pairing; target_stage's five enum values and their ordering are left entirely to the schema.

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 a specific action pair (advance a simulated delivery to a later stage, or reject it with a reason) applied to a clearly qualified resource ('simulated delivery', 'mock/sandbox'). That qualifier is what separates it from real lifecycle tools like cancel_delivery or dispatch_robot, so an agent can tell it is the demo/test variant without opening the schema.

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?

'Testing only (mock/sandbox)' is an explicit when-to-use gate and effectively an exclusion from production use. It does not name an alternative tool to use for real lifecycle changes, so the negative guidance is implied rather than routed, which keeps it below a 5.

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