Skip to main content
Glama

Order status

get_order_status

With the order_token create_order gave: this order's status and its crypto block. Or with order_id and operator_key, for the operator whose key made the order: pending_review while a person has not approved the operator, else the payment service's order view (held and why, quoted and the quote, paid, expired or denied). Paid publishes nothing by itself.

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
order_idNo
order_tokenNo
operator_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / order_token
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "order_id",
      -  "operator_key"
      -]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose meaningful traits: operator lookups return pending_review until a human approves the operator, otherwise the payment-service view, and 'paid publishes nothing by itself' warns of a non-obvious side effect. However it is silent on authorization failures, invalid/expired tokens, and rate limits, and never defines what a 'crypto block' is, so it falls short of full disclosure for an unannotated tool.

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

Conciseness3/5

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

The token mode is front-loaded, which is good, but the body is two dense run-on sentences with elliptical phrasing ('held and why, quoted and the quote') and an unexplained 'crypto block'. It is compact but not cleanly readable; a short bulleted mode/state structure would serve better.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description does substitute a state enumeration (pending_review, held with reason, quoted with quote, paid, expired, denied), which is the most valuable thing it could add. But it leaves the crypto block unexplained and says nothing about failure modes, so it is not complete relative to the tool's complexity.

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 must supply meaning, and it does: order_token is the value produced by create_order, while order_id and operator_key are used together and are scoped to the operator key that made the order. The mutual-exclusivity of the two modes is only implied by 'Or', and operator_key format is not specified.

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?

The description names a specific verb+resource: fetch one order's status ('this order's status and its crypto block'), and it ties the tool back to create_order as the source of the token. It is clearly distinguishable from create_order/list_products, though the term 'crypto block' is never explained, leaving part of the resource vague.

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 gives two explicit calling modes: order_token (as handed back by create_order) or order_id plus operator_key for the operator that created the order. That is real routing guidance rather than an implication. It does not say what happens if both modes are supplied, nor which combination to prefer when both are available.

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