Skip to main content
Glama

Purchase number

purchase_number
Destructive

Buy a phone number for your account (free sandbox numbers with test keys). Live numbers are billed monthly.

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": {
      "phone_number": "<phone_number>"
    },
    "name": "purchase_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idNoOptional: assign the number to one of your customers
phone_numberYesThe number to buy, in E.164
idempotency_keyNoOptional. Retries are already safe: the same call with the same inputs within 10 minutes is done once and answers with the first result. Pass your own key to dedupe across a longer gap, or a new one to repeat an identical call on purpose.
registration_idNoOptional (live numbers): the registration this number should send for. Without it the number follows your account's registration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / phone_number / description
      Added value: +"The number to buy, in E.164"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds useful cost/environment context: sandbox numbers are free with test keys, while live numbers incur monthly billing. It does not describe permissions or reversibility, but with annotations present this is a solid addition.

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 cost note; no 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?

For a purchase mutation with rich parameter descriptions and annotations, the description covers what the tool does and the key billing/sandbox distinction. It omits prerequisite discovery and alternatives, but remaining gaps are minor.

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 explains phone_number E.164, customer_id, idempotency_key, and registration_id in detail. The description adds no parameter-specific meaning, so baseline 3 applies.

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?

The description names a specific verb and resource: "Buy a phone number for your account." It clearly conveys the action, though it does not explicitly differentiate from siblings such as bulk_purchase_numbers or search_available_numbers.

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

Usage Guidelines2/5

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

It gives no conditional when-to-use guidance and does not name alternatives such as bulk_purchase_numbers for multiple purchases or search_available_numbers for finding a number. The sandbox/live billing note is context, not usage routing.

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.