Skip to main content
Glama

twilio_release_number

Release a connected Twilio phone number to stop its service and end monthly charges.

Instructions

(Beta) Release a phone number (PN…) of a connected Twilio account: it stops working, its monthly charge sto...

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_release_number"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose the key consequence: the number "stops working" and its monthly charge ceases, which signals a destructive, effectively irreversible action. However, the sentence truncates before finishing, and it says nothing about permissions required, whether release can be undone, or error behaviour for numbers not on the account.

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 useful content is front-loaded and short, but the text is truncated mid-sentence ("its monthly charge sto…"), leaving an incomplete clause. The "(Beta)" marker is the right place for a caveat, but overall the definition reads as an unfinished excerpt rather than a self-contained statement.

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 destructive, no-parameter, no-annotation, no-output-schema tool, the description should clarify how the target number and account are determined — presumably from connected-account context. It omits that entirely, so an agent cannot tell from the definition alone how to invoke it correctly or what happens on success or failure.

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 takes zero parameters, so the baseline is 4. The description does not need to explain any inputs, though it also never explains which number is targeted given the absence of a number parameter.

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?

"Release a phone number (PN…) of a connected Twilio account" gives a specific verb and resource, and the inverse relationship to twilio_buy_number is inferable. It stops short of naming any sibling or stating the account-scoping rule explicitly, and the sentence is cut off before completing its point.

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?

There is no when-to-use guidance, no prerequisite conditions (e.g. the number must be owned by the connected account), and no mention of an alternative path such as twilio_api_request. The agent must infer the trigger condition entirely from the verb.

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