Skip to main content
Glama

Check a number order

get_order
Read-only

Check a phone number order from buy_numbers by order_id or customer_reference to view status, delivered numbers, and charges; requires an API key.

Instructions

Check a number order from buy_numbers: status (provisioning, partially_fulfilled, fulfilled, delayed, cancelled, closed_refunded), the numbers delivered so far and what was charged. Pass the order_id or your customer_reference. Needs your API key.

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": "<order>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesThe order_id or the customer_reference.

Output Schema

NameRequiredDescriptionDefault
voiceYes
statusYes
billingYes
numbersYes
orderedYes
order_idYes
days_paidYes
deliveredYes
created_atYes
charged_usdYes
outstandingYes
completed_atYes
refunded_usdYes
customer_referenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the full status vocabulary (provisioning through closed_refunded), the fact that partial delivery is possible ('partially_fulfilled', 'the numbers delivered so far'), and the API key requirement.

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?

Purpose is front-loaded, followed by return contents, then accepted identifiers and auth. The parenthetical status list is dense but earns its place as an enum reference; the closing 'Needs your API key' is a terse fragment that reads slightly clipped.

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 full annotations and an output schema, this covers identification, expected return content, and auth. Nothing critical is missing, though a note on behavior for unknown order references would round it out.

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 100% for the single 'order' parameter, and the description's 'Pass the order_id or your customer_reference' simply restates the schema's own wording. Baseline 3 applies since the schema already carries the parameter semantics.

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 gives a specific verb-and-resource ('Check a number order from buy_numbers') and enumerates exactly what comes back: status, delivered numbers, and charges. That separates it from siblings like get_activation and list_my_numbers, though it never names an alternative 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?

Usage is implied rather than stated: you check an order after buy_numbers, and it tells you to supply order_id or customer_reference. There is no guidance on when to prefer this over get_activation or list_my_numbers, and no mention of error or not-found conditions.

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