numero-virtual-mcp

Pedir um numero

request_number

Buy a virtual number for SMS verification, with balance debited immediately; returns activation ID and phone number so you can wait for the code or cancel.

Instructions

Compra um numero virtual para receber o SMS de verificacao de um servico. Debita o saldo na hora. Devolve o id da ativacao e o telefone; depois use wait_for_sms (ou get_activation) para ler o codigo. O numero vale ~20 minutos; se o SMS nao vier, cancele com cancel_activation para o valor voltar ao saldo.

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": {
      "serviceId": "<serviceId>"
    },
    "name": "request_number"
  }
}

Input Schema

Name	Required	Description	Default
`ddd`	No	Somente Brasil: DDD de 2 digitos desejado. Pode ter taxa adicional.
`apiId`	No	Opcao (fornecedor) especifica, de list_services. Sem isso a API escolhe a mais barata com estoque.
`country`	No	Codigo ISO do pais. Padrao: BR.	BR
`serviceId`	Yes	ID do servico, de list_services.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that the balance is debited immediately (a real cost side effect), the ~20-minute lifetime of the number, and that cancellation refunds the value. It also tells the agent what the call returns (activation id and phone).

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?

Four tightly packed sentences: action and cost first, then the return value and next step, then the time limit and refund path. No sentence is redundant and the most decision-relevant facts (cost, expiry, refund) are front-loaded.

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

Completeness5/5

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

There is no output schema and no annotations, so the description must cover the return and safety profile itself — and it does, naming the returned activation id and phone plus the expiry/refund behavior. Nothing an agent needs to invoke this correctly is missing.

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 the schema already documents all four parameters (ddd, apiId, country, serviceId) and their defaults. The description adds no parameter-level detail beyond the schema, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Compra um numero virtual') plus the exact purpose (receber o SMS de verificacao). It also names what is returned and routes the agent to siblings, so it is distinguishable from the other activation tools at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit follow-up routing: use wait_for_sms or get_activation to read the code, and cancel_activation if the SMS never arrives. The ~20-minute validity window tells the agent when the number expires, which is exactly the condition that selects the cancel path.

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

Deploy Server