Skip to main content
Glama
Smitline: AI Phone Calls & Meetings

Smitline: AI Phone Calls & Meetings

End a call

end_call
Destructive

Wrap up an active call politely and hang up, or cancel a call that has not connected yet by providing the call ID.

Instructions

Ask the assistant to wrap up politely and hang up, or cancel a call that has not connected yet.

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": "end_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
callIdYesCall id returned by start_call, such as call-0123456789abcdef

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is largely covered. The description adds real context beyond that: the assistant speaks a polite wrap-up before hanging up, and the tool doubles as a cancel path for unconnected calls. It does not say whether the action is irreversible, what happens to the call record or transcript, or what a caller hears on the cancel path, which caps it at 3.

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?

One sentence, no filler, and the primary action is front-loaded ahead of the secondary cancel case. Every clause carries information the agent needs to choose the right mode.

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 single-parameter, no-output-schema tool the description is nearly sufficient: it covers both connected and not-yet-connected states and explains the observable behavior of the hang-up. The remaining gap is post-termination semantics, such as whether the call record persists or whether the outcome is retrievable via get_call.

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?

There is a single parameter with 100% schema description coverage, including an example call id format, so the schema does the heavy lifting and the baseline of 3 applies. The description adds only indirect meaning, implying via the cancel mode that the id may reference a call that has not yet connected. No format or lookup guidance is added beyond the schema.

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 states a specific verb (end/hang up) applied to a specific resource (a call), and it usefully splits the behavior into two modes: a polite wrap-up for a live call and a cancellation for a call that never connected. An agent can tell this apart from transfer_call_to_me or wait_for_call without opening the schema. It falls short of a 5 only because it never names the sibling it is an alternative to.

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

Usage Guidelines4/5

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

Two clear usage conditions are given: use it to finish a conversation politely, or to cancel a call still pending connection. That is genuine when-to-use context keyed to call state. It stops short of explicit exclusions, such as preferring transfer_call_to_me when the goal is to hand the caller off rather than terminate.

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