Skip to main content
Glama

Delivery timeline

get_delivery_events
Read-onlyIdempotent

Every event on the delivery in order: created, funded, dispatching, offers, assigned, each driver step, delivered, confirmed, paid, plus messages.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful content-level behavior: the result is a chronologically ordered event stream that includes driver steps and messages. It omits pagination, volume limits, or behavior for deliveries with no events, which matters for a potentially long timeline.

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 front-loaded sentence with zero filler; the ordering guarantee comes before the event enumeration. The long comma-separated list of lifecycle stages is information-dense rather than padded, though it reads as a raw enumeration rather than a structured breakdown.

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?

This is a simple read-only single-parameter tool with no output schema, so the description's enumeration of returned event types is doing real work in describing the return shape. What remains missing is guidance on when to prefer it over get_delivery_messages and any note on result size or pagination.

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 required parameter delivery_id, so the schema contributes only the name and type. The description's phrase 'on the delivery' implies the parameter scopes to one delivery, but adds no format, example, or source for the ID. With only one parameter this is a modest gap, hence a middle score.

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 states a specific resource and ordering guarantee ('every event on the delivery in order') and enumerates the event types returned, so an agent knows exactly what it gets back. It does not, however, differentiate itself from siblings like get_delivery or get_delivery_messages, and the trailing 'plus messages' actually blurs the boundary with get_delivery_messages.

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 when-to-use guidance and no named alternative. An agent must infer from 'in order' that this is the audit/timeline view, and must guess whether to call get_delivery_messages separately or whether messages are already included here.

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.