Skip to main content
Glama

Hang up phone call

hangup_call
DestructiveIdempotent

Cancel or hang up a call you own. Idempotent; may return leg_stop_pending when carrier hang-up has not completed, including for finalized calls with outstanding cleanup. Retry the same call id.

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": {
      "call_id": "<call_id>"
    },
    "name": "hangup_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
call_idYesCall id to cancel or hang up.

Output Schema

NameRequiredDescriptionDefault
statusYes
call_idYes
messageYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description's 'Idempotent' merely echoes that. What it genuinely adds is the leg_stop_pending outcome, including for finalized calls with outstanding cleanup, and the correct recovery action (retry the same call id). That is useful behavior beyond the annotations, though it says nothing about latency or what cleanup entails.

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?

Three short sentences with the action front-loaded, followed by the idempotency/edge-case caveat and the recovery step. Nothing is redundant and every clause carries information an agent needs.

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

Completeness5/5

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

An output schema exists, so return-value shape need not be re-explained, yet the description still flags the one return state that changes agent behavior. For a destructive single-parameter mutation with full annotation coverage, nothing material is missing.

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?

Schema description coverage is 100% for the single call_id parameter, so the schema already carries the documentation burden and 3 is the baseline. The description adds only the retry-identity nuance ('retry the same call id'), which is mild but relevant value.

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 gives a specific verb pair and resource: 'Cancel or hang up a call you own.' That is unambiguous and cannot be confused with siblings such as get_call or place_call. It does not explicitly name a sibling alternative, so it lands at 4 rather than 5.

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?

It establishes a precondition ('a call you own') and gives a concrete retry instruction for the leg_stop_pending case, which is real operational guidance. It does not state when to prefer this over any other tool or describe any exclusion beyond ownership, so usage is implied rather than fully framed.

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.