Skip to main content
Glama

Check an order

get_order
Read-only

Retrieve a confirmed order's status, items, and payment details by order_id. customer_email is required as soft-auth and must exactly match the order record, prevents arbitrary order lookups. Returns payment status (paid | pending | failed), production status, and dispatch date once available.

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

Input Schema

NameRequiredDescriptionDefault
order_idYes
customer_emailYes

Output Schema

NameRequiredDescriptionDefault
itemsNo
paid_atNo
currencyYes
order_idYes
lead_timeNo
total_zarYes
order_statusNo
payment_statusYes
order_referenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: customer_email acts as soft-auth and must exactly match, which prevents arbitrary lookups. It stops short of describing what happens on a mismatch (error shape, whether it leaks existence), which is the one notable gap.

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?

Three tight sentences, front-loaded with what is retrieved and then the auth constraint. The final sentence restating return values partially duplicates the existing output schema, which is the only wasted space.

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 two-parameter read with full annotation coverage and an output schema, this is nearly complete: purpose, auth behavior, and result fields are all covered. Missing only failure-mode behavior when the email does not match.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden and does so: order_id is the lookup key and customer_email is a soft-auth credential requiring an exact match. That is real meaning beyond the bare string types, though no format or case-sensitivity details are given.

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 (retrieve a confirmed order) plus the exact fields returned (status, items, payment details), keyed by order_id. The word 'confirmed' implicitly separates it from the cart/checkout siblings in the catalog without needing to name them.

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?

Clear context for use: only confirmed orders, and the caller must supply both order_id and the matching customer_email. It never explicitly says when to prefer get_cart or get_checkout instead, so there are no stated exclusions or alternative routing, keeping it below a 5.

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