Skip to main content
Glama

check_twilio_number

Repair / re-sync the Twilio SMS/voice webhook configuration for a number (useful when call/SMS routing breaks). This does not check WhatsApp Cloud API health. Pass the full request body for /utils/twilio/check-number as an object — typically includes phoneNumber or phoneNumberSid.

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": {
      "payload": "<payload>"
    },
    "name": "check_twilio_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesFull request body object for /utils/twilio/check-number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, so the mutation/safety profile is covered structurally. The description adds the useful negative scope 'does not check WhatsApp Cloud API health' and implies the webhook config gets overwritten, but does not state permissions needed, reversibility, or what happens to the prior webhook state — a notable gap for a repair tool.

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

Conciseness4/5

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

Three tight sentences, each doing distinct work: what it does, its trigger, its negative scope, and the payload shape. Front-loaded with the action; no filler.

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 mutation tool with a free-form nested payload and no output schema, the description covers the essentials but leaves the payload contract underspecified ('typically includes' hints at other required keys) and says nothing about the response or post-repair state. Adequate but incomplete.

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 schema's single 'payload' property is a free-form nested object with no enumerated fields, so the schema alone cannot tell an agent what to put in it. The description compensates by noting the body typically includes phoneNumber or phoneNumberSid and points at the target endpoint, which is meaningfully more than the schema provides.

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?

Names a specific verb+resource: 'Repair / re-sync the Twilio SMS/voice webhook configuration for a number', which resolves the ambiguity of the name 'check_twilio_number' (which sounds read-only). It distinguishes from WhatsApp explicitly, but does not differentiate from the near-duplicate sibling sync_sms_twilio_number.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Useful when call/SMS routing breaks' gives a trigger condition, which is real usage guidance. However, with sibling sync_sms_twilio_number and release_twilio_number present, the description offers no explicit alternative routing or when-not-to-use rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources