numero-virtual-mcp

Pedir reenvio do SMS

resend_sms

Requests a fresh SMS verification code for the same virtual number activation when the original message does not arrive and the provider allows resending.

Instructions

Pede ao fornecedor um novo SMS para a mesma ativacao (quando o servico permite reenviar o codigo). Use se o primeiro nao chegou.

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": {
      "id": "<id>"
    },
    "name": "resend_sms"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	ID da ativacao.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A3.8/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. It usefully discloses the precondition that the downstream service must allow resending, but says nothing about failure modes, cost implications, rate limits, or whether the original activation state changes.

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 short sentences, front-loaded with the action and then the use condition; there is no redundant or filler text.

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?

For a one-parameter action with no output schema and no annotations, the description covers what it does, the precondition, and when to invoke it. It is nearly sufficient, missing only outcome/failure behavior for a resend request.

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?

Only one parameter (id), and schema description coverage is 100% ('ID da ativacao'), so the schema already documents it fully. The description adds no format, range, or sourcing detail beyond the schema, making the baseline 3 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?

States a specific verb+resource: requesting a fresh SMS from the provider for the same activation. It is clearly distinguishable from siblings like request_number, wait_for_sms and cancel_activation, though it does not explicitly name any sibling for contrast.

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

Usage Guidelines4/5

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

"Use se o primeiro nao chegou" gives a clear triggering condition, and the parenthetical narrows it further to cases where the service permits a resend. No alternative tool is named (e.g. wait_for_sms first), so it stops short of explicit when-not guidance.

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

Deploy Server