Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

get_proxy_pricing

Proxy traffic prices: the three types (residential, mobile, datacenter) with the price per GB, order limits and volume discounts. Requires the proxies scope.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does add real context by naming the required 'proxies' scope and describing the shape of the returned pricing data, but it never states explicitly that the call is read-only, whether prices are cached/currency-specific, or that it has no side effects.

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 compact sentences, front-loaded with the resource and its contents, followed by the auth requirement. Every clause (types, per-GB price, order limits, volume discounts) carries distinct information with no 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?

With no output schema, the description must convey return values, and it does so by listing the returned pricing facets. The auth scope is also covered; only minor gaps remain, such as currency or per-location pricing granularity and whether results are live.

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?

The tool takes zero parameters, so parameter semantics are not a source of ambiguity and the baseline is 4. The description correctly implies no input is needed and focuses entirely on the returned data.

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 resource (proxy traffic prices) and enumerates what it reports: the three proxy types, price per GB, order limits and volume discounts. This clearly separates it from get_number_pricing or generic get_pricing without opening a schema.

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 only implied by the nature of a pricing lookup; there is no explicit statement of when to call this versus get_pricing or get_proxy_plan, nor any prerequisite flow (for example, call before get_proxy_order). Adequate but leaves routing to inference.

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