Skip to main content
Glama
AiAgency-Now

VoiceAI-MCP-VAVicky

Official
by AiAgency-Now

disconnect_twilio

Disconnect your Twilio account from VoiceAI-MCP-VAVicky to manage integrations and control platform connections.

Instructions

Disconnect Twilio account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execution handler for the 'disconnect_twilio' tool. It sets the URL to the /twilio/ endpoint and method to DELETE, which disconnects the Twilio account by making an HTTP DELETE request.
    case 'disconnect_twilio':
      url = `${this.baseUrl}/twilio/`;
      method = 'DELETE';
      break;
  • index.js:325-333 (registration)
    The registration of the 'disconnect_twilio' tool in the ListTools response, including its name, description, and input schema (no required parameters).
    {
      name: 'disconnect_twilio',
      description: 'Disconnect Twilio account',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • The input schema for the 'disconnect_twilio' tool, defining an empty object with no properties or required fields.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Disconnect' implies a destructive operation, but it doesn't clarify whether this is reversible, what data might be affected, or if it requires specific permissions. For a potentially impactful tool with zero annotation coverage, this is a significant gap in transparency.

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 phrase that directly states the tool's purpose without any fluff. It's appropriately sized for a zero-parameter tool and front-loads the essential information. Every word earns its place.

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

Completeness3/5

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

Given the tool's complexity (likely moderate due to 'disconnect' implying account-level changes), lack of annotations, and no output schema, the description is minimally adequate. It states what the tool does but doesn't cover behavioral aspects like effects or return values. For a tool that could have significant side effects, more context would be beneficial.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline high score. However, it doesn't reach 5 because it could optionally mention that no inputs are required, though this isn't necessary.

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 'Disconnect Twilio account' clearly states the action (disconnect) and the resource (Twilio account). It distinguishes from siblings like 'connect_twilio' and 'update_twilio_number' by indicating a termination action rather than connection or modification. However, it doesn't specify what 'disconnect' entails (e.g., removing integration, revoking tokens, or deleting data), keeping it from a perfect score.

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 an active connection first), consequences (e.g., loss of functionality), or related tools like 'connect_twilio' for re-establishing the account. This lack of context leaves the agent guessing about appropriate usage scenarios.

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