Skip to main content
Glama
AiAgency-Now

VoiceAI-MCP-VAVicky

Official
by AiAgency-Now

get_twilio_numbers

Retrieve all Twilio phone numbers associated with your VoiceAI platform for managing voice and AI chat integrations.

Instructions

Get all Twilio phone numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:334-342 (registration)
    Registration of the 'get_twilio_numbers' tool in the ListToolsRequestSchema handler, including its name, description, and input schema.
    {
      name: 'get_twilio_numbers',
      description: 'Get all Twilio phone numbers',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Input schema for the 'get_twilio_numbers' tool: no required parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
  • Handler implementation in executeTool method: constructs the API URL `/twilio/numbers` and performs a GET request via fetch to retrieve Twilio phone numbers.
    case 'get_twilio_numbers':
      url = `${this.baseUrl}/twilio/numbers`;
      break;
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Get all Twilio phone numbers' but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, pagination, or what the return format looks like (e.g., list of numbers with details). This is a significant gap for a tool with no annotation coverage.

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?

The description is a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse. Every word earns its place by directly conveying the tool's purpose.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'all' entails (e.g., owned numbers, pagination), the return format, or any behavioral context. For a tool that likely interacts with an external API (Twilio), more details on authentication, error handling, or response structure would be helpful.

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?

The input schema has 0 parameters with 100% description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate since none are needed. A baseline of 4 is applied as it correctly aligns with the schema's completeness.

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 clearly states the verb 'Get' and resource 'all Twilio phone numbers', making the purpose unambiguous. It distinguishes from siblings like 'get_available_numbers' (which likely shows purchasable numbers) and 'update_twilio_number' (which modifies numbers). However, it doesn't specify if this retrieves numbers owned by the account or all numbers in Twilio's inventory, 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing Twilio connection via 'connect_twilio'), exclusions, or comparisons to siblings like 'get_available_numbers' or 'get_twilio_usage'. Usage is implied only by the tool name and description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AiAgency-Now/MCP-VoiceAI-WhiteLabel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server