Skip to main content
Glama

twilio_buy_number

Purchases a phone number for a connected Twilio account. Use it after finding an available number with the search tool.

Instructions

(Beta) Buy one phone number for a connected Twilio account (find one with twilio_search_available_numbers).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "twilio_buy_number"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses very little. It does not mention that purchase incurs recurring cost, whether the action is reversible, which number will be provisioned, what errors are raised, or what the call returns. '(Beta)' is the only extra context offered.

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?

A single short sentence that is front-loaded with the core action and appends the prerequisite in a parenthetical. No filler or redundancy.

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

Completeness2/5

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

This is a zero-annotation, mutating, spend-incurring operation with no output schema, so the description should explain cost, irreversibility, and number selection. Instead it says nothing about consequences or results, which is insufficient for a purchase action.

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?

The schema has zero parameters, so there is no parameter meaning to add and the baseline would normally be 4. But the absence of any number-selection input is a real semantic gap: the description says 'buy one phone number' without explaining how that number is chosen, leaving the operation partially opaque to the caller.

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 ('Buy one phone number') and scopes it to a connected Twilio account, which clearly separates it from twilio_search_available_numbers and twilio_list_numbers. It does not distinguish itself from other mutating siblings such as twilio_release_number, but the action itself is unambiguous.

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?

The parenthetical tells the agent to locate a number first with twilio_search_available_numbers, implying a prerequisite step. However, it never states when not to use it, what happens if no numbers are available, or how it relates to release/disconnect tools, so guidance is implied rather than explicit.

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

Deploy Server

Other Tools