Skip to main content
Glama

disconnect_twilio

Removes a Twilio account’s stored credentials from this Mac’s Keychain and disconnects that account from LMCP.

Instructions

(Beta) Disconnect a Twilio account from LMCP: its credential is deleted from this Mac's Keychain and the tw...

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

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?

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral context by stating that the credential is deleted from this Mac's Keychain, which tells the agent the action has a persistent local side effect. However, it never says whether the operation is reversible, whether the underlying Twilio account is affected, or what happens to in-flight integrations, and the sentence is truncated before the second consequence is revealed.

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

Conciseness2/5

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

The text is short and front-loads the verb and resource, which is good. But it ends mid-word ('the tw...'), so the structure is broken and a stated consequence is left dangling, which is a defect rather than conciseness.

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?

For a zero-parameter disconnect tool with no output schema and no annotations, the description needs to explain the effect and whether it can be undone. It covers the Keychain credential deletion but omits reversibility, the state of the Twilio account itself, and what the caller should do next. The truncation leaves the second half of the consequence unknown.

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 there is no parameter meaning for the description to add; the baseline of 4 applies. The description does not need to compensate for any schema gap here.

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 names a specific verb and resource: 'Disconnect a Twilio account from LMCP'. That is enough to separate it from the many twilio_* operation tools (send_message, list_calls, etc.) and from connect_twilio. It stops short of 5 only because the sentence is cut off before it finishes describing what else is removed.

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 explicit when-to-use or when-not-to-use guidance. It does not say to call connect_twilio to re-establish the link, nor whether other Twilio tools will fail after disconnection. The reader must infer the context from the name and the word 'Disconnect'.

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