Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

hangup_call

End an active phone call by providing its unique call ID. Use this tool to terminate a call that is in progress; if the call is already ended, the action has no effect.

Instructions

End an in-progress call immediately. No-op / error if the call already terminated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_idYes

Implementation Reference

  • Handler function for the 'hangup_call' tool. Accepts a call_id string, delegates to the Agentline client's hangup() method, and returns the result or an error dict.
    @mcp.tool()
    def hangup_call(call_id: str) -> dict:
        """End an in-progress call immediately. No-op / error if the call already
        terminated.
        """
        try:
            return _client_or_init().hangup(call_id)
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • Registration of 'hangup_call' as an MCP tool via the @mcp.tool() decorator from FastMCP.
    @mcp.tool()
    def hangup_call(call_id: str) -> dict:
  • Helper function that lazily initializes and returns the shared Agentline client instance used by hangup_call.
    def _client_or_init() -> Agentline:
        global _client
        if _client is None:
            _client = _build_client()
        return _client
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool is a no-op or returns an error if the call already terminated, but lacks details on permissions, side effects, or response format.

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?

Two sentences with no redundant information. Every word contributes to clarity: action, state requirement, and edge-case behavior.

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 simple tool with one parameter and no output schema, the description covers the core purpose and key behavioral nuance (no-op on already terminated). Missing details like error type or return value are minor. Overall adequate.

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

Parameters2/5

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

The input schema has one required parameter (call_id) with no description, and schema description coverage is 0%. The description does not add any meaning for this parameter, such as format, source, or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('End an in-progress call') and the resource ('in-progress call'). It distinguishes from siblings like make_call or get_call, and includes the immediate effect and edge case ('No-op / error if already terminated').

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?

No explicit guidance on when to use this tool versus alternatives (e.g., get_call, list_numbers). It indicates the tool is for ending an active call but does not compare to sibling tools or provide exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jgottlieb84/agentline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server