Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

order_virtual_number

Rent a virtual number from the balance. type "unlimited" receives SMS from every service; type "service" is dedicated to one service (pass its id from get_number_pricing). pool picks MAIN or EXTRA for an unlimited number where get_number_pricing lists pools (when omitted, the pool it names in unlimitedPool); tell the user first when the chosen term is not cancellable, and which pool's numbers are.

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>",
      "term": "<term>"
    },
    "name": "order_virtual_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolNoUnlimited only: the pool to buy from, from pools in get_number_pricing (default: its unlimitedPool)
termYesRental term
typeNoNumber type (default unlimited)
countryYesISO country code
serviceNoService id for a dedicated number
nicknameNoUnlimited only: a label
autoRenewNoUnlimited only: renew from the balance before expiry

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pool / description
      Previous value: -"Unlimited only: the pool to buy from, from pools in get_number_pricing (default EXTRA)"New value: +"Unlimited only: the pool to buy from, from pools in get_number_pricing (default: its unlimitedPool)"
  2. Changed1 schema field changed
    • addedInput schema / properties / pool
      Added value: +{
      +  "description": "Unlimited only: the pool to buy from, from pools in get_number_pricing (default EXTRA)",
      +  "enum": [
      +    "MAIN",
      +    "EXTRA"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.7/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 usefully discloses that the purchase draws from the balance and instructs the agent to warn the user upfront when the term is non-cancellable and about pool assignment, but says nothing about failure modes, whether the rental is reversible, or what the call returns.

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-loads the action and packs the mode/pool rules into a single compact passage with no filler. The trailing clause about warning the user is grammatically awkward and slightly harder to parse than the rest.

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 7-parameter mutating tool with no annotations and no output schema, the description covers the core selection logic and the user-facing warning obligation. It leaves gaps on return value, failure handling, and how nickname/autoRenew interact with the order, which matters given the absence of structured behavioral hints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining what "unlimited" versus "service" actually does and where the service id comes from (get_number_pricing). It does not touch nickname or autoRenew, which the schema covers on its own.

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 ("Rent a virtual number from the balance") and immediately distinguishes the two modes ("unlimited" vs "service"). It does not differentiate itself from the sibling order_number, so it falls short of a 5.

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?

Gives clear conditional routing: type "unlimited" for SMS from every service, "service" for one service with its id taken from get_number_pricing, and pool only for unlimited numbers. Lacks explicit when-not guidance (e.g., versus order_number) or prerequisites such as balance requirements.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources