Skip to main content
Glama

List deliveries

list_deliveries
Read-onlyIdempotent

status='active' or a comma list; since ISO datetime.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
offsetNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description contributes no additional behavior: no default ordering, no pagination defaults, no note on which deliveries are included (active vs. all) or what the listing returns.

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

Conciseness2/5

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

It is short, but brevity here is under-specification rather than concision — two clipped fragments with no subject, verb, or sentence structure. Nothing is front-loaded because there is no opening statement of what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter list tool with no output schema and no documented params, the description should explain what a delivery listing contains, how paging works, and what the status filter actually selects. None of that is present, so an agent must guess most operational details.

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%, so the description must carry the load, and it does partially: it gives the accepted status value ('active' or a comma list) and the ISO datetime format for 'since', which the schema does not convey. However, 'limit' and 'offset' get no mention (defaults, max, pagination semantics), leaving half the parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a parameter fragment ('status=...', 'since ISO datetime') and never states what the tool does. The only signal that this lists deliveries is the name and title, so the text effectively adds nothing about purpose or scope (e.g., which deliveries, whose, in what workspace).

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 guidance at all: nothing about when to call this versus get_delivery, list_delivery_events-style siblings, or cancel/confirm operations. The status filter hint implies a use case but never names an alternative or a condition for selecting this tool.

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.