Skip to main content
Glama

Open call audio

open_call_audio
Destructive

Call card only: a single-use WebSocket URL for the call's live audio. talk takes the call over from the browser.

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>",
      "mode": "<mode>"
    },
    "name": "open_call_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
call_idYes
card_idNo

Output Schema

NameRequiredDescriptionDefault
urlYes
expires_inYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / card_id
      Added value: +{
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
  2. Added

TDQS

B3.1/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 safety profile is partly covered. The description adds real context beyond that: the URL is single-use (expires after one connection) and talk mode transfers audio control away from the browser, which explains the destructive hint. It still does not say what happens to the existing browser session or whether the call remains open.

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 short sentences, front-loaded with the returned artifact and followed by the mode caveat; nothing is padded. It is arguably over-compressed, since the terse phrasing of "Call card only" costs clarity rather than saving space.

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

Completeness2/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 shape need not be described, but this is a destructive control-transfer operation with three undocumented parameters and an unexplained precondition. For that complexity the definition leaves too much for the agent to infer before invoking it.

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?

Schema description coverage is 0%, so the description carries the full burden, yet it explains only the talk value of mode and never mentions call_id or the optional card_id. Worse, "Call card only" suggests card_id is central while the schema marks it optional, leaving the caller unsure when to supply it.

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 outcome: a single-use WebSocket URL for the call's live audio, which is a specific resource plus deliverable rather than a restatement of the name. It does not differentiate from plausible siblings such as take_over_call or get_call, and the qualifier "Call card only" is left unexplained.

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" implies a scope restriction (not usable for arbitrary calls) and "talk takes the call over from the browser" implies when to pick the talk mode. However, neither is framed as explicit when-to-use/when-not guidance, and no alternative tool is named for the non-card case.

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.