Skip to main content
Glama

Track delivery

track_delivery
Read-onlyIdempotent

Live status, ETA, driver position and last event. Poll this every 30–60s while active. The delivery card shows these details: reply in one short line instead of repeating them.

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuinely non-structured context: the data is live and should be polled at 30–60s, and the UI already displays these details so the reply should be one short line instead of a dump – that reply-shaping rule is behavior an agent would not otherwise know.

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 compact sentences, front-loaded with what the tool returns and then the operating instructions. No filler, no restatement of the title.

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?

There is no output schema, so the description must convey return content – it does by enumerating status, ETA, driver position, and last event. Combined with polling cadence and the reply-shaping rule, an agent has enough to call and report correctly; only the delivery_id semantics remain 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 0% for the single delivery_id parameter, so the description carries some burden but says nothing about the identifier's format, source, or valid values. With only one parameter this is a minor gap, but the description adds no meaning beyond 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 concrete return content – live status, ETA, driver position, last event – which is far more specific than the title 'Track delivery'. It does not, however, distinguish itself from sibling get_delivery or get_delivery_events, so an agent must infer that this is the live/polling view rather than the static snapshot.

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?

'Poll this every 30–60s while active' gives real operational guidance on cadence and on when polling matters (while the delivery is active). It does not say when to prefer this over get_delivery or get_delivery_events, and the reply-format instruction, while useful, is about presenting results rather than tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.