Skip to main content
Glama

order_status

Look up a paid order by its public reference (G77-YYYYMMDD-…). Returns outcome, ready time, total, and whether a $5 refund is due. Does not return customer phone or address.

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": {
      "ref": "<ref>"
    },
    "name": "order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose the return payload (outcome, ready time, total, refund flag) and deliberate omissions (phone, address). It stops short of stating auth requirements, not-found behavior, or whether the $5 refund flag is informational only.

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 sentences, both front-loaded and free of filler: the first defines the lookup and its key, the second bounds the return payload.

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?

No output schema exists, so the description responsibly enumerates the returned fields and the excluded ones. What is missing is the domain of 'outcome' and the failure mode for an invalid or unpaid reference.

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% and the only property is an untyped string, so the 'G77-YYYYMMDD-…' format hint in the description is real added value an agent cannot get from the schema. It does not say whether the reference is case-sensitive or validated.

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 paid order') plus the scoping constraint that only paid orders are covered, which separates it from place_order and quote_order without naming them. Slightly short of 5 because it never explicitly contrasts with a sibling.

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?

'paid order' and 'by its public reference' imply the preconditions for use, and the phone/address exclusion hints at the privacy-safe path. However, no alternative tool is named and nothing says what to do for an unpaid or unknown reference.

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