Skip to main content
Glama

get_order_status

Look up a purchase by its order ID or original request ID without waiting for SMS.

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": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNo
order_idNo
request_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; 'look up' reasonably signals a non-mutating read and the non-blocking SMS note is genuinely useful context. It says nothing about the api_key credential, failure behavior for unknown IDs, or rate limits, which for a zero-annotation tool is a meaningful gap.

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?

A single front-loaded sentence with no filler; the identifiers and the latency benefit both appear before any trailing clause. Nothing could be cut without losing 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?

An output schema exists, so return values need no explanation, and the intended lookup path is clear. The main omission is the api_key requirement and what happens when both or neither identifier is provided, given all three parameters are optional with no defaults documented.

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 compensate; it does so partly by naming order_id and request_id and framing them as alternatives ('or'), which the schema does not express. The third parameter, api_key, is never mentioned, and precedence when both identifiers are supplied is left unresolved.

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 ('Look up a purchase') plus two accepted identifiers, which clearly separates it from siblings like order_history and wait_for_code. It never names those siblings explicitly, so differentiation is inferred rather than stated.

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?

'Without waiting for SMS' implicitly positions this against a blocking code-wait tool, giving an agent a usable selection cue. However, there is no explicit when-to-use/when-not guidance and no statement of what to do if neither identifier is at hand.

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.