numero-virtual-mcp

Concluir ativacao

complete_activation

Mark a virtual number activation as completed after using its SMS code. Optional step that releases the number earlier.

Instructions

Marca a ativacao como concluida depois de usar o codigo. Opcional, mas libera o numero mais cedo.

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

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.5/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add a genuine behavioral fact beyond the name: the call is optional but frees the number earlier, which hints at a resource-release side effect. It omits error behavior, idempotency, and what happens if the activation is already completed.

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?

One compact sentence with the action front-loaded and the optional/benefit nuance appended. Every clause earns its place; nothing is padded.

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

Completeness3/5

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

For a single-parameter mutation with no annotations and no output schema, the description covers the essential behavior and the optional nature of the call. It still leaves the agent without error semantics or confirmation of what completion changes beyond freeing the number.

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% with a single documented 'id' parameter, so the schema already carries the parameter meaning. The description adds nothing about the parameter, which is acceptable given full coverage but not additive.

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: marking an activation as complete. It is distinguishable from siblings like cancel_activation and get_activation by the outcome described, though it never explicitly contrasts itself with 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?

"Depois de usar o codigo" gives a timing condition for use, and "Opcional" signals it is not mandatory. However, it offers no guidance on when to prefer cancel_activation or what happens if the activation is never completed, leaving the alternatives entirely to inference.

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

Deploy Server