Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

list_proxy_plans

Your proxy plans, one per type bought: host, ports, login, password and the traffic left. refresh=true reads the traffic figures again.

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_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoRead the traffic figures again

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose the return contents (host, ports, login, password, traffic left) and the refresh behavior. It omits whether the call is scoped to the authenticated account, whether refresh triggers a live re-fetch with any delay or quota cost, and how traffic figures are sized/formatted.

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?

Two short sentences, front-loaded with the purpose before the refresh caveat; nothing is padded. The phrase 'one per type bought' is slightly compressed and could be read ambiguously, but it earns its place by conveying the result cardinality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read with one optional flag and no output schema, the description does cover the field list, which is the main missing structured information. It still leaves the return container shape (array? keyed by type?), what 'type' enumerates, and freshness semantics underspecified.

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% and there is just one optional boolean, so the schema already defines it. The description's 'refresh=true reads the traffic figures again' essentially restates the schema text, adding only the implication that traffic numbers may otherwise be cached/stale.

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 uses a clear verb-and-resource framing ('Your proxy plans, one per type bought') and enumerates the returned fields, so an agent can tell this is a listing of the caller's own plans. It stops short of explicitly distinguishing itself from the single-plan siblings (get_proxy_plan, list_proxy_plan), leaving that inference to the name.

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?

'Your proxy plans' implies the caller should use this to see plans already purchased, which is useful implied guidance. There is no explicit when-to-use/when-not statement and no pointer to the single-plan retrieval tools or the orders tools for buying new plans.

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