Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

get_number_pricing

Prices of virtual numbers in one country: every unlimited term (12h, 1d, 7d, 30d, 180d, 365d) and every dedicated-service offer with its terms. Where the country has two pools of unlimited numbers, pools lists MAIN and EXTRA with each term's price and whether it is cancellable, and unlimitedPool names the one an order without a pool buys from.

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": {
      "country": "<country>"
    },
    "name": "get_number_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesISO country code, e.g. "GB"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does substantial work: it discloses the return shape (per-term prices, cancellability, pool selection semantics for orders without a pool). It does not state that the call is read-only, nor mention auth, rate limits, or currency of the prices, which are meaningful gaps for an unannotated tool.

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?

Purpose is front-loaded in the first clause, and the remaining clauses add genuinely useful detail about terms and pools. The single dense sentence with nested clauses about `pools` and `unlimitedPool` is slightly hard to parse, but nothing is redundant.

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?

There is no output schema, so the description must explain return values, and it does so in detail, including the pool structure and cancellability flag. It leaves open the price currency and what 'dedicated-service offers' entail, which are the remaining gaps for a pricing lookup.

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?

There is a single required parameter with 100% schema coverage, and the schema already documents it as an ISO country code. The description only restates the country scoping ('in one country') without adding format, validation, or fallback behavior, so baseline 3 is appropriate.

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 definition names a specific resource and scope: pricing of virtual numbers for a single country, covering every unlimited term and every dedicated-service offer. It even explains the pool structure (MAIN vs EXTRA, `unlimitedPool`). It never contrasts itself with the sibling pricing tools (get_pricing, get_proxy_pricing), so it stops short of full sibling differentiation.

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 rather than stated: fetch it when you need number prices for a country. There is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives such as get_number_renewal_options or get_pricing, so the agent must infer which pricing tool applies.

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