Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

list_proxy_orders

List your proxy traffic orders, newest first. Filter by type or status (PENDING, COMPLETED, FAILED).

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": "list_proxy_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
typeNoThe proxy type
limitNoResults per page (default: 20, max: 100)
statusNoFilter by status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the sort order and that results are scoped to 'your' orders. It omits return shape, pagination defaults, and any auth or rate-limit context, which is a meaningful gap for an unannotated tool even if the operation is low risk.

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 the resource and ordering front-loaded and the filtering capability second. Nothing is repeated unnecessarily and nothing is filler.

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 simple read-only list tool with no output schema and fully described parameters, the description covers what it returns (proxy orders), the ordering, and the available filters. It could add a note on pagination behavior or what an empty result means, but the essentials are present.

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 100%, so every parameter already has documented meaning and both enum sets are defined in the schema. The description restates the status values and names the type/status filters without adding semantics beyond them, matching the baseline for a fully documented schema.

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?

States a specific verb and resource ('List your proxy traffic orders') plus an ordering guarantee ('newest first'), which cleanly separates it from the sibling 'list_esim_orders' and 'list_active_orders'. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

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 resource name and the two filter dimensions, but there is no guidance on when to choose this over 'list_active_orders' or 'get_proxy_order'. It also doesn't say whether filters combine or how filtering by both behaves.

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