Skip to main content
Glama

One order in full

get_order
Read-onlyIdempotent

Returns one of the signed-in account's orders by its reference: each line's product, ship-to state and recorded reading, the rules quoted with their sources, and on the Record plan the lot each line shipped from, that lot's confirmed certificate, the consent recorded and what happened after the sale. Does not count as a lookup.

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": {
      "reference": "<reference>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesThe order's reference as the store sent it, or as list_orders shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the baseline is met. Beyond that the description discloses plan-dependent return behavior (the Record plan adds lot, confirmed certificate, recorded consent and post-sale outcome) and a non-obvious accounting trait ('Does not count as a lookup'), which is genuine value not available in structured fields.

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?

Front-loaded with the verb and identifier, followed by a dense but purposeful enumeration of returned fields. The long field list is heavy but every clause names a distinct piece of returned data; the one-word-audience exclusion sentence at the end earns its place.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly, including plan-conditional fields. Minor gaps remain: totals/pricing, pagination-irrelevance, and failure behavior for an unknown reference are unstated, but for a single-record read tool this is close to sufficient.

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 coverage is 100% and the schema already explains the reference format ('as the store sent it, or as list_orders shows it'). The description adds only 'by its reference', which duplicates the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Returns one of the signed-in account's orders by its reference') and scopes it to the signed-in account, then enumerates the returned contents. It implicitly separates itself from list_orders ('one ... order by reference') and explicitly from a lookup ('Does not count as a lookup'), but it never names the sibling, so differentiation is inferential rather than direct.

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?

Usage is only implied: an agent can gather it is for fetching a known reference rather than browsing, and that it is not a metered lookup. There is no explicit 'use list_orders to find references first' routing, no statement about what to do when the reference is unknown, and no prerequisites.

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