Skip to main content
Glama

Hang up a call

hangup_call
DestructiveIdempotent

Ends one call that is in progress, identified by its 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": {
      "callId": "<callId>"
    },
    "name": "hangup_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
callIdYesThe call's id, as returned when the call was placed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / callId / description
      Previous value: -"The callId returned by outbound_call"New value: +"The call's id, as returned when the call was placed"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered. The description adds only the scoping detail that it acts on a single in-progress call; it says nothing about what happens if the call has already ended, whether the hangup is immediate, or any error behavior.

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?

A single front-loaded sentence with no filler; the verb and scope arrive first and nothing redundant follows.

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

Completeness4/5

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

For a one-parameter termination tool with a rich annotation set and no output schema, the description covers the essentials. The only meaningful gap is the absence of guidance about preconditions (call must still be live) and what an agent should expect on failure.

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% and the single callId parameter is fully documented in the schema as "the call's id, as returned when the call was placed." The description merely restates that the call is identified by its id, adding no new meaning or format detail.

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 ("Ends") and resource ("one call that is in progress"), so an agent can immediately tell this is a termination action rather than a status or listing query. It does not explicitly name a sibling such as outbound_call or call_status, so differentiation is implied by the verb rather than stated.

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?

The phrase "in progress" implies the precondition for use, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to alternatives. The agent must infer that live calls should be checked via siblings like calls_live or call_status before invoking this.

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.