Skip to main content
Glama

buy_temp_number

Purchase a private temporary phone number for a selected country and service to receive SMS verification codes and OTPs.

Instructions

Buy a private temporary phone number (paid, requires API key in env).

Args: country: Country code — e.g. "russia", "usa", "india". service: Target service — e.g. "telegram", "whatsapp", "google", "any". provider: 5sim | smspool

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>",
      "service": "<service>"
    },
    "name": "buy_temp_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes
serviceYes
providerNo5sim

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two important traits: the operation costs money and requires an API key in the environment. It stays silent on other material behavior for a purchase tool — price/credits consumed, whether the number is reserved or reusable after purchase, what happens when a provider is out of stock, and refund behavior. Useful but incomplete.

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?

Front-loaded one-line purpose followed by a compact Args list — no wasted prose. The docstring-style formatting is functional rather than polished, 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?

An output schema exists, so return values need not be described, and the description covers purpose, prerequisite cost/auth, and per-parameter examples. What remains missing — pricing, number lifetime, failure modes — is partly mitigated by the output schema but would still be valuable for a paid operation.

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 0% with three undocumented properties, so the description must compensate. It supplies concrete example values for country ('russia', 'usa', 'india'), service ('telegram', 'whatsapp', 'google', 'any'), and the two provider options ('5sim' | 'smspool'), which materially helps. It still omits the fact that provider defaults to 5sim and gives no strict enumeration or case-format rules, leaving ambiguity about valid inputs.

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 — 'Buy a private temporary phone number' — with the key qualifier that it is paid and needs an API key. That distinguishes it implicitly from the free-number siblings (list_free_sms_numbers, read_free_sms), though it never names them.

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?

The parenthetical 'paid, requires API key in env' gives a real prerequisite for use, which is more than most. However, there is no guidance on when to pick this over list_free_sms_numbers / read_free_sms, or how it relates to check_paid_sms after purchase — the agent must infer that flow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.