Skip to main content
Glama
Sign In
io.github.stucchi/telnyx

io.github.stucchi/telnyx

by stucchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

order_phone_number

Order and purchase a specific phone number through the Telnyx API. Provide the desired phone number to complete the transaction.

Instructions

Order/purchase a phone number.

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

Input Schema

NameRequiredDescriptionDefault
phone_numberYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'order/purchase' but omits details about charges, payment method requirements, or the result of the action (e.g., immediate activation).

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?

The description is a single sentence containing the essential action. It is concise, though it could be slightly more structured with separate lines for behavior and parameter details.

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?

For a transactional tool with one parameter and no annotations, the description is incomplete. It does not explain what happens after ordering, what the output schema contains, or any error cases.

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

Parameters1/5

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

The single parameter 'phone_number' has 0% schema description coverage. The tool description does not add any format, constraints, or examples, leaving the agent to guess the valid format (e.g., E.164).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'order/purchase' and the resource 'phone number', which distinguishes it from sibling tools like 'get_phone_number' 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?

No guidance is provided on when to use this tool versus alternatives like 'search_available_numbers' (to find numbers) or 'list_phone_numbers' (to see existing ones). There is no mention of prerequisites or conditions.

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