Skip to main content
Glama

Get delivery

get_delivery
Read-onlyIdempotent

Full delivery by id or short code (RD-XXXXXXX). Hosts that support MCP Apps render a live tracker card. 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": "get_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds genuinely new context: hosts with MCP Apps render a live tracker card, and the agent should reply in one short line rather than restating the card contents — a behavioral nuance absent from annotations.

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

Conciseness3/5

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

Purpose is front-loaded and the text is short, but the final sentence ("The delivery card shows these details: reply in one short line instead of repeating them.") is garbled and reads as two fused thoughts, costing clarity.

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?

For a single-parameter read tool with no output schema, the description covers the input format and the rendering/response expectation. The main omission is any pointer to sibling tools for events, messages, or tracking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (a bare string with no description), so the description carries the burden. It specifies the parameter accepts either a delivery id or a short code with the format example RD-XXXXXXX, which is real meaning the schema does not provide.

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?

"Full delivery by id or short code" names the resource and the lookup key, which is enough to separate it from list_deliveries and get_delivery_events. It stops short of saying how it differs from track_delivery, but the verb+resource is concrete.

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 explicit guidance on when to choose this over track_delivery, get_delivery_events, or list_deliveries. The only usage-like instruction concerns how to format the reply when a card renders, which is output guidance 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.