Skip to main content
Glama

Get order status

get_order_status
Read-only

Get the status of an order by its ID or token. Returns order status, type, pricing, and provisioned resource details when available.

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
idNoThe order ID (MongoDB ObjectId)
tokenNoThe order token (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description adds value by enumerating what is returned (status, type, pricing, provisioned resources) and hedging with 'when available', but it does not say what happens for an unknown ID/token or whether fields can be absent for pending orders.

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 short sentences with zero filler; the action and the return payload are both front-loaded.

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 read-only, two-parameter lookup with no output schema, the description covers input identity and the shape of the response well. Only the not-found / partial-data behavior is left unstated.

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?

With 100% schema coverage the baseline is 3, but the description contributes the key semantic that either an ID or a token identifies the order — important since the schema marks neither parameter required and provides no one-of constraint. It does not state precedence if both are supplied.

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?

Specific verb plus resource: 'Get the status of an order'. The agent knows exactly what entity is being queried, though it does not name a sibling to distinguish from (siblings are domain/VPS/webspace tools, so overlap is low anyway).

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 implied by the lookup framing — fetch status for a known order — but there is no explicit when-to-use, when-not-to-use, or reference to an alternative tool. Nothing is misleading; guidance is just thin.

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.