Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

get_proxy_order

One proxy order. Poll it while its status is PENDING: it becomes COMPLETED or FAILED within a few minutes.

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": {
      "orderId": "<orderId>"
    },
    "name": "get_proxy_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesThe order id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 burden and does deliver real behavior: the returned record has a status field with three enumerated values, and terminal status arrives "within a few minutes," which sets polling expectations. It omits what happens for an unknown or expired orderId and doesn't explicitly confirm the call is non-mutating, which keeps it short of a 5.

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 front-loaded sentences with zero filler: the first names the resource, the second gives the operational instruction and the expected timing. Nothing could be removed without losing signal.

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 getter with no output schema, knowing there is a status state machine and how long transitions take is the essential missing context, and it is supplied. The residual gap is that the other returned fields are unnamed, but without an output schema that is a minor omission rather than a blocking one.

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?

Single required parameter with 100% schema description coverage, so the schema already defines orderId. The description adds only the implicit point that the id must reference an existing order (the one being polled), which is marginal but not misleading.

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?

"One proxy order" plus the PENDING/COMPLETED/FAILED lifecycle clearly identifies this as the single-record fetch by order id, distinct in spirit from list_proxy_orders. It never states an explicit verb ("retrieve"/"fetch") and doesn't contrast itself with the similarly named get_order or get_esim_order, so an agent must infer the scope difference from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Poll it while its status is PENDING" is genuine when-to-use guidance with an implied stop condition (COMPLETED/FAILED). It does not name any alternative or say what to do if the caller only has partial information, so there is no explicit exclusion or sibling routing.

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