Skip to main content
Glama
Sign In

Voxisim

by com.voxisim
OverviewDiscussionsAdmin

List one-time number countries

sms_activation_list_countries
Read-only

One-time SMS numbers. List countries available for a service, with price and availability, for one verification method (verification_type, default sms).

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": {
      "service_id": "<service_id>"
    },
    "name": "sms_activation_list_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_idYesService id from sms_activation_list_services
verification_typeNoHow the code arrives: sms (default), call (flash call — the caller's number is the code) or voice (a bot reads the code out; also catches SMS and flash calls). Each has its own countries and prices.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results carry price and availability, which is genuine behavioral context, but says nothing about ordering, empty-country cases, or per-method price variance beyond the schema's own note.

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?

Two short sentences with the resource and the scoping dimension front-loaded. The opening fragment 'One-time SMS numbers.' is slightly clipped but functions as an effective category cue rather than filler.

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?

With an output schema present, return shape need not be explained, and annotations cover safety. Both parameters are fully documented in the schema, so the description carries only what is needed for a read-only listing tool.

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%, including a detailed enum explanation for verification_type, so the baseline is 3. The description only restates the sms default and does not add meaning beyond what the schema already spells out.

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: list countries available for a service, scoped to one-time SMS numbers and a single verification method. The 'one-time' qualifier and the required service_id implicitly separate it from sms_rental_list_countries, though the sibling is never named.

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 only implied: the schema notes service_id comes from sms_activation_list_services, which hints at the call order. The description itself gives no explicit when-to-use versus sms_rental_list_countries or sms_activation_list_numbers, and no statement about when this is not appropriate.

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

All Voxisim toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources