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

io.github.stucchi/telnyx

by stucchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_phone_number

Retrieve details of a specific phone number by providing its ID. Access information like carrier, capabilities, and status.

Instructions

Get details of a specific 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_id": "<phone_number_id>"
    },
    "name": "get_phone_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
phone_number_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are present, and the description simply says 'Get details,' which implies a read operation. It fails to disclose any behavioral traits such as error handling (e.g., if ID not found), rate limits, or authentication requirements, which the description should cover in lieu of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise and front-loaded. However, it is overly terse and lacks substantive information, making it more under-specified than efficiently concise.

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?

Given the single required parameter with no description and no annotation coverage, the description is incomplete. The existence of an output schema reduces the need to explain returns, but the input parameter details are missing, making the tool hard to use correctly without external knowledge.

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?

Schema description coverage is 0%, and the tool description provides no additional meaning beyond the parameter name 'phone_number_id.' The name itself is somewhat descriptive, but the description does not clarify format, constraints, or expected values, leaving the agent with no guidance on what to provide.

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 uses the verb 'Get' and specifies the resource 'details of a specific phone number,' making the tool's action clear. It distinguishes from sibling tools like list_phone_numbers, but does not specify what details are included, leaving some ambiguity.

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 list_phone_numbers or other getters. There is no mention of prerequisites or exclusions, leaving the agent to infer usage context.

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