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

Smitline: AI Phone Calls & Meetings

Take over a phone call

transfer_call_to_me
Destructive

Transfers a connected phone call to your own phone when you ask to take over, so you can continue the conversation directly.

Instructions

Hand a connected phone call to the user's own phone. Only when the user asks to take over.

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

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.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risky profile is known. The description adds that the call must be "connected" and that it goes to the user's own phone, but never states what the agent loses after handoff, whether the call stays alive, or what happens if transfer fails.

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 short sentences, zero filler, with the action front-loaded and the constraint immediately after. Nothing could be removed without losing information.

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?

For a destructive, non-idempotent single-action tool, the definition covers the what and the when but lacks post-transfer behavior and failure conditions. Adequate to invoke correctly, thin for predicting the outcome.

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 coverage is 100% and the single callId parameter is fully documented in the schema, including an example format tied to start_call. The description adds no further meaning about the parameter, so baseline 3 applies.

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?

States a concrete verb and resource: handing a connected phone call over to the user's own phone. It is clearly distinguishable from siblings like end_call or start_call, though it never names them explicitly.

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?

The clause "Only when the user asks to take over" gives an explicit trigger and implicit exclusion, which is real guidance rather than none. It stops short of naming what to do otherwise (e.g., use end_call or send_call_instruction instead), so it is not a full 5.

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