Skip to main content
Glama

taufnaus Geschenke-Shop

Bestellstatus

get_order_status
Read-onlyIdempotent

Status of an order created with checkout (waiting for payment, paid, shipped with tracking number).

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is fully covered without the description. The description adds value by sketching the return states and noting that shipped orders carry a tracking number, which is the only return-value information available since there is no output schema. It omits error behavior for unknown or unpaid orders and whether the status list is exhaustive.

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?

One front-loaded sentence with no waste, and the status enumeration is placed where an agent will read it first. The parenthetical is packed but readable.

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?

For a simple single-parameter read tool with full safety annotations, the definition covers the essentials but leaves gaps: no statement on what happens for a nonexistent or unpaid order, no clarification of order_id format, and no confirmation that the status list is complete. It is adequate but not complete.

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 0%, so the single order_id parameter is documented only by its name and type. The description partially compensates by tying it to a checkout-created order, hinting at provenance and distinguishing it from other order identifiers. It still gives no format, length, or validation details for order_id.

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 resource (order status) and enumerates the possible states (waiting for payment, paid, shipped with tracking number), which tells the agent exactly what kind of answer to expect. It distinguishes itself implicitly from checkout (which creates the order) but never names a sibling explicitly.

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?

The phrase 'order created with checkout' implies the prerequisite and suggests the order_id originates from the checkout tool, which is useful routing context. There is no explicit when-to-use/when-not guidance or mention of alternatives such as get_cart, so usage is only implied.

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