Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

Dispatch robot

dispatch_robot

Send a robot to fulfill an approved delivery quote, creating the real job and incurring the quoted fee. Use only after the user confirms the fee and pickup/dropoff details.

Instructions

Send a robot to fulfil a quote from get_delivery_quote. This creates a real delivery and incurs the quoted fee (outside mock mode). Only call it after the user has seen the fee and addresses and explicitly said yes; set confirmed=true only in that case. Pickup and dropoff are taken from the quote and can't be changed.

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": {
      "quote_id": "<quote_id>",
      "confirmed": "<confirmed>",
      "items": "<items>",
      "recipient_name": "<recipient_name>"
    },
    "name": "dispatch_robot"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesWhat is being delivered
quote_idYesquote_id from get_delivery_quote
confirmedYesMust be true, and only after the user explicitly approved this quote's fee
pickup_notesNoInstructions for loading
dropoff_notesNoInstructions for the handoff
recipient_nameYes
recipient_phoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description adds real value by disclosing that this creates an actual delivery and charges the quoted fee outside mock mode. It also discloses an immutability constraint (pickup/dropoff are fixed by the quote), which no annotation conveys. It stops short of covering retries/idempotency behavior or how to undo a mistaken dispatch (e.g., via cancel_delivery), so a 4 rather than a 5 is defensible.

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?

Three sentences, no filler: the action and the quote dependency come first, the real-world cost and confirmation gate second, the immutability constraint last. Every sentence carries a decision-relevant fact.

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?

Covers the costly, irreversible-in-spirit action and its user-consent gate well, which is the main risk for a dispatch tool with openWorldHint. However, there is no output schema, and the description never says what a successful call returns (delivery id, tracking handle) or how to follow up, which an agent needs after the call.

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 71%, so most parameters are already documented in the schema, and the description largely reinforces the confirmed flag rather than adding new meaning. The one genuinely new constraint, that pickup and dropoff cannot be changed, concerns fields that are not parameters at all, leaving recipient_name and recipient_phone undocumented in both places. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Send a robot to fulfil a quote") and ties itself directly to the sibling get_delivery_quote that produces the required quote_id. An agent can distinguish it from cancel_delivery, track_delivery, or get_delivery_quote immediately.

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

Usage Guidelines5/5

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

Gives explicit preconditions: call only after the quote exists, only after the user has seen the fee and addresses, and only after an explicit yes, with confirmed=true reserved for that case. This is a clear when-to-use contract with a hard gate rather than vague guidance.

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