Skip to main content
Glama

Download delivery

fetch_delivery
Read-only

After payment, use the delivery token to list files or read rows. Every delivery lists json (the original records) and fields.json (which requested fields were found, with path and type) together. csv and xlsx appear only when the records are already flat and do not replace fields.json. rows pages the original records. A paid excess-rows add-on has its own extra.json and extra.fields.json, plus extra.csv and extra.xlsx only when those rows are flat. XLSX is returned as base64 bytes with its content type. All rows pages for a file count once per token; a full download counts once each. On expiry or download_limit, call get_order with your order capability for a fresh token. A current session is required and the delivery token is bound to it. If the original session expired, initialize a new one and call get_order first.

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": {
      "order_id": "<order_id>",
      "delivery_token": "<delivery_token>"
    },
    "name": "fetch_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
formatNo
offsetNo
order_idYesOrder number, e.g. GMD7K3P9Q. Lowercase or hyphenated input (gmd-7k3p9q) is accepted.
delivery_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, and the description adds substantial behavioral context beyond that: token/session binding, how rows pages are counted, how full downloads are counted, expiry/download_limit recovery, and XLSX base64 return behavior. This is exactly the kind of operational detail an agent needs.

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?

The description is dense but front-loads the core action, then provides format and recovery details. Given the tool's format complexity, the length is largely justified, though the long paragraph could be structured more clearly.

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 tool with five parameters, low schema coverage, and no output schema, the description covers the important delivery-format behavior, token/session requirements, counting rules, and error recovery. It still leaves limit/offset paging and delivery_token semantics implicit, which keeps it from being fully complete.

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 only 20%, with order_id documented but delivery_token, limit, and offset undocumented. The description partly compensates by explaining format values such as json, fields.json, csv, xlsx, rows, and the extra add-on files, but it does not explain limit/offset paging semantics or the delivery token parameter in detail.

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

Purpose5/5

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

The description states a specific verb and resource: use a delivery token after payment to list files or read rows from a delivery. It also names get_order as the alternative when the token expires or hits download_limit, so the agent can distinguish this tool from the order-management sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the post-payment context and says to call get_order for a fresh token on expiry or download_limit, including the session-expiry recovery path. It does not explicitly contrast all sibling tools, but the main alternative is named with its triggering condition.

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.

Resources