Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_live_close

Idempotent

Close your live session asynchronously, drain running speech and produce recordings. Poll job_get.

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": {
      "job_id": "<job_id>",
      "session_key": "<session_key>"
    },
    "name": "switchboard_live_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
session_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, idempotent, non-destructive, so the safety bar is partly covered. The description adds real behavioral context beyond them: the operation is asynchronous, it drains in-flight speech, it yields recordings, and progress requires polling a job tool. It does not explain where the required job_id comes from, which an agent would want to know.

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 compact sentences, front-loaded with the action and followed by the required next step. No padding or repetition of schema fields.

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 an async mutation flow with no output schema and zero parameter documentation, the description covers the action and the polling contract but omits parameter provenance and what the produced recordings look like or where they surface. Adequate to initiate the call, not complete enough to call it confidently.

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% — neither job_id (32-hex pattern) nor session_key (32-128 chars) has any documented meaning. The description never mentions either parameter, leaving the agent to guess that job_id is a previously returned job handle and session_key identifies the live session. With both parameters required and completely undocumented, the description fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Close your live session') plus the secondary effects ('drain running speech and produce recordings'), which is materially more informative than the name alone. An agent can distinguish it from siblings like switchboard_live_extend or switchboard_dante_glasses_close because it is clearly the session-termination operation.

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?

Explicitly says to poll switchboard_job_get after the call, giving the required follow-up flow for an async operation. It stops short of stating when not to use it (e.g., versus switchboard_live_extend for keeping a session alive), so no exclusions are provided.

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.

Resources