Skip to main content
Glama

get_order_status

Read-only

Checks a fictional order's status after verifying the order reference and customer email, so support agents can answer order-status questions.

Instructions

Read the status of a fictional order. Requires the order reference and the matching email supplied by the customer.

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

Input Schema

NameRequiredDescriptionDefault
emailYes
order_idYes

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context the schema cannot express: the email must be the matching one on the order, making this a verification-gated lookup, and the data is explicitly fictional. It omits what happens on a mismatch (error vs empty result), which is the main remaining 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?

Two sentences, front-loaded with the action and followed by the prerequisite. Every clause carries information and there is no redundant framing.

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?

With an output schema present, return values need not be explained, and both required parameters are given meaning. For a simple read tool this is nearly complete; the only missing piece is failure behavior when the email does not match the order.

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 description coverage is 0%, so the description must carry the load, and it does: it clarifies that order_id is a customer-supplied reference and that email must match the order rather than acting as a free filter. It does not restate the ORD-#### pattern, which the schema already encodes via regex, so nothing important is missing.

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 states a specific verb and resource: "Read the status of a fictional order." It is immediately distinguishable from siblings like create_return_request or get_help_article by resource domain. It stops short of naming an alternative, but the purpose itself is unambiguous.

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?

It implies the usage context (customer supplies both an order reference and their email, so this is a customer-facing lookup), but gives no explicit when-to-use/when-not-to-use rules and does not route to any sibling tool. Adequate but leaves the agent to infer the boundary conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.