Skip to main content
Glama

twilio_get_call

Retrieve details for one Twilio call by its SID, including from, to, status, start and end times, and duration. Use the SID from a call list to inspect a single call.

Instructions

(Beta) Read one Twilio call by its SID (CA…, from twilio_list_calls): from, to, status, start and end, dura...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that this is a single-record read, flags the tool as "(Beta)", and enumerates the returned fields (from, to, status, start/end). It says nothing about authentication prerequisites, rate limits, or error behavior for an invalid SID, and the field list is truncated before it finishes.

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 single-sentence, front-loaded structure is efficient and puts the SID requirement early. However, the description is visibly truncated ("dura..."), leaving a dangling clause that reads as an incomplete definition rather than a deliberately terse one.

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?

There is no output schema, so the field enumeration is carrying real weight — and it is cut off, so the agent cannot fully know what it receives. Combined with the zero-parameter schema conflicting with the stated SID requirement, an agent lacks enough information to invoke this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema declares zero properties, yet the description tells the agent to supply a SID — a genuine mismatch between definition and schema rather than mere under-documentation. The description does add useful meaning about the SID's origin and format (CA prefix, sourced from twilio_list_calls), but the missing-parameter discrepancy prevents a higher score.

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 ("Read one Twilio call") and identifies the unique key (SID, prefixed CA…), which separates it from twilio_list_calls and twilio_create_call. It also previews the returned fields, so an agent can tell what the tool yields, though the text is cut off mid-word ("dura...") and the intended scope statement never completes.

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?

"by its SID (CA…, from twilio_list_calls)" implies a workflow: obtain a SID via twilio_list_calls, then fetch details here. That is a useful implied usage rule, but there is no explicit when-not guidance and no statement about what to do if the SID is unknown or the call is missing.

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