Skip to main content
Glama

Connect the user to a call

take_over_call
Destructive

Call card only: rings the account's loop-in contacts one at a time, or its verified phone when none are set, and connects the first phone that answers, voicemail included. The phone agent first tells the other side it is connecting them, then stops for good once a phone answers.

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

Input Schema

NameRequiredDescriptionDefault
call_idYesCall id of the live, answered call to connect the user to.
card_idNo

Output Schema

NameRequiredDescriptionDefault
call_idYes
messageYes
takeoverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / card_id
      Added value: +{
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / takeover / oneOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "at": {
      -        "type": "string"
      -      },
      -      "state": {
      -        "const": "ringing",
      -        "type": "string"
      -      },
      -      "via": {
      -        "const": "phone",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "via",
      -      "state",
      -      "at"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "at": {
      -        "type": "string"
      -      },
      -      "state": {
      -        "const": "connected",
      -        "type": "string"
      -      },
      -      "via": {
      -        "enum": [
      -          "phone",
      -          "browser"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "via",
      -      "state",
      -      "at"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "at": {
      -        "type": "string"
      -      },
      -      "state": {
      -        "const": "unanswered",
      -        "type": "string"
      -      },
      -      "via": {
      -        "const": "phone",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "via",
      -      "state",
      -      "at"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "at": {
      +        "type": "string"
      +      },
      +      "state": {
      +        "const": "ringing",
      +        "type": "string"
      +      },
      +      "via": {
      +        "const": "phone",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "via",
      +      "state",
      +      "at"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "at": {
      +        "type": "string"
      +      },
      +      "state": {
      +        "const": "connected",
      +        "type": "string"
      +      },
      +      "via": {
      +        "enum": [
      +          "phone",
      +          "browser"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "via",
      +      "state",
      +      "at"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "at": {
      +        "type": "string"
      +      },
      +      "state": {
      +        "const": "unanswered",
      +        "type": "string"
      +      },
      +      "via": {
      +        "const": "phone",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "via",
      +      "state",
      +      "at"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, but the description adds real substance beyond them: sequential ringing of loop-in contacts, fallback to the verified phone, voicemail counting as an answer, the announcement the phone agent makes, and the fact that it terminates permanently once a phone answers. It omits auth/permission requirements and any rate or cost implications of ringing multiple contacts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the scoping constraint front-loaded and no filler. The phrase 'stops for good once a phone answers' is slightly colloquial but still conveys the terminal behavior efficiently.

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?

An output schema exists, so return values need no explanation, and the destructive behavior is well covered. The remaining gap is the undocumented card_id parameter, which an agent must guess at in a two-parameter mutation tool.

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 50%: call_id is fully described in the schema, while card_id has no description anywhere. 'Call card only' hints that card_id identifies the call card context, but the description never explains what card_id does or whether it is optional. Baseline 3 applies since the schema carries half the burden.

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 concrete action sequence: rings the account's loop-in contacts one at a time, falls back to the verified phone, and connects the first phone that answers. The leading 'Call card only' scopes it away from the generic place_call/hangup_call siblings, though it never names an alternative tool explicitly.

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?

'Call card only' establishes a context precondition, and the 'live, answered call' requirement in the schema narrows it further. However, there is no explicit when-not guidance and no named alternative for placing a fresh call instead of taking over an existing one.

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.