Skip to main content
Glama

get_order

Read-onlyIdempotent

One order by order_id: its status and, once paid, the delivery. To list all your orders use my_orders. Needs your key.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoyour key, if your client cannot send headers
order_idYesOrder id from buy or my_orders, e.g. "or_…".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "your key, if your client cannot send headers",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / order_id / description
      Added value: +"Order id from buy or my_orders, e.g. \"or_…\"."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds value on top: the auth requirement, and the non-obvious conditional behavior that the delivery field only appears once the order is paid. It does not mention what happens for an unknown or unauthorized order_id, which keeps it short of a 5.

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

Conciseness5/5

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

Two short sentences with no waste: the core behavior is front-loaded, then the disambiguation, then the auth note. Every clause carries distinct information.

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 simple read tool with full annotation coverage and a fully documented schema, the description covers purpose, alternative, prerequisites, and the shape of the result even without an output schema. Only error/empty-result behavior is unaddressed, which is a minor gap.

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 100%, so both parameters are already documented, including the "or_…" id format and the api_key fallback for header-less clients. The description only reinforces that api_key is needed for auth, adding little beyond 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.

Purpose5/5

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

States a specific verb and resource (fetch one order by order_id) and goes further by naming the payload (status, and delivery once paid). It also names the sibling tool it is not (my_orders), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this for a single order, use my_orders to list all orders. It also states the prerequisite ("Needs your key"), so both the selection condition and the setup requirement are covered in one line.

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