Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

order_proxies

Buy proxy traffic from the balance. The first order of a type creates a plan and returns its login and password; later orders add traffic to the same plan. Pass the quoted total as expectedTotal. Never repeat this call after a timeout or an error without checking list_proxy_orders first.

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": {
      "type": "<type>",
      "gb": "<gb>"
    },
    "name": "order_proxies"
  }
}

Input Schema

NameRequiredDescriptionDefault
gbYesWhole gigabytes
typeYesThe proxy type
expectedTotalNoThe price from quote_proxies; a different price now charges nothing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/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 so well: it discloses that money is spent from the balance, that the first call for a type creates a durable plan and returns credentials, that subsequent calls mutate that same plan, and that a mismatched expectedTotal results in no charge. It also flags the idempotency hazard (timeout/error retries) which is exactly the behavior an agent would otherwise get wrong.

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?

Three sentences, front-loaded with the core action, then lifecycle behavior, then the safety rule. Every sentence carries distinct information; nothing is padding.

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 mutation tool with no annotations and no output schema, this is close to complete: cost source, plan creation, credential return, price protection, and retry safety are all covered. The only gap is what a later (top-up) order returns, since only the first-order response shape is described.

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 coverage is 100%, so the baseline is 3, and the description mostly restates what the schema already says about expectedTotal. It does add a small amount of workflow meaning by framing it as "the quoted total" to be passed through, but it says nothing extra about gb or the type enum beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Buy proxy traffic from the balance") and goes further by explaining the lifecycle semantics: the first order of a type creates a plan and returns login/password, later orders top it up. That distinguishes it clearly from quote_proxies (pricing) and list_proxy_orders (inspection), both of which are referenced.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use (buying traffic with a quoted price) and an explicit when-not-to-repeat rule: "Never repeat this call after a timeout or an error without checking list_proxy_orders first." It also routes the agent to obtain the price before calling via the quoted-total instruction, so no inference is required.

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