Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

Track delivery

track_delivery
Read-only

Retrieve a delivery's current status, robot position, and ETAs by delivery ID to monitor progress.

Instructions

Current status, robot position and ETAs for a delivery.

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>"
    },
    "name": "track_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYesDelivery id returned by dispatch_robot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 output context (status, robot position, ETA) but says nothing about data freshness, whether the snapshot is live or cached, or how unknown/invalid delivery ids behave.

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?

One compact sentence that front-loads what the caller gets back, with zero filler. It is a noun phrase rather than a verb phrase, which slightly weakens the action framing, but nothing is wasted.

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 one-parameter read tool with annotations and full schema coverage, the definition covers purpose and the shape of the response. With no output schema, though, naming 'status' and 'ETAs' without indicating their possible values or units leaves the return payload only loosely specified.

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% and the single parameter is documented as 'Delivery id returned by dispatch_robot', which already covers format and provenance. The description adds no further meaning about the id, so the baseline 3 applies.

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 resource (a delivery) and the three things it reports: current status, robot position, and ETAs. That is enough to distinguish it from list_deliveries or get_delivery_route without opening the schema, but it never explicitly contrasts itself with those siblings.

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?

There is no when-to-use or when-not-to-use guidance. An agent is left to infer that this is a status-polling call and gets no help deciding between it and simulate_delivery_progress or get_delivery_route, which could plausibly overlap.

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