Skip to main content
Glama

Get order status

get_order_status
Read-onlyIdempotent

Retrieves order status, shipped line quantities, and tracking details for a buyer's company order using its order number, so you can confirm fulfillment progress and delivery status.

Instructions

Status, lines with shipped quantities, and tracking for one order belonging to the buyer's company.

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

Input Schema

NameRequiredDescriptionDefault
order_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior, so the description need not repeat that. It does add a real constraint beyond annotations — that lookups are scoped to the buyer's company — plus the shape of the payload. It says nothing about behavior for unknown or unauthorized order numbers.

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?

A single compact sentence with no filler, and the most useful information (what comes back, and the single-order scope) is front-loaded. It reads as a noun phrase rather than a full sentence, but nothing is wasted.

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?

For a one-parameter read tool with no output schema, the description is sufficient: it states the resource, the access boundary, and the returned data at a useful level of detail. Remaining gaps (not-found handling, identifier source) are minor for this complexity.

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%, but there is only one required parameter and its name (order_number) plus the pattern in the schema make the format self-evident. The description confirms the tool operates on a single order, but adds no guidance on the identifier's expected format or source.

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 resource (one order) and enumerates the returned facets: status, lines with shipped quantities, and tracking. The phrase 'one order' distinguishes it from list-style siblings such as list_orders, though the verb itself is only implied by the title.

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?

Usage is only implied: 'one order' suggests a single-record lookup rather than a listing, and 'belonging to the buyer's company' hints at an access scope. No alternative tool is named and no conditions for choosing this over list_orders or search_parts are stated.

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