Whisper

agents: disconnect

whisper_agents_disconnect

The disconnect operation on the Whisper control plane, served as CALL whisper.agents({op:'disconnect', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.disconnect","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "whisper_agents_disconnect"
  }
}

Input Schema

Name	Required	Description	Default
`input`	No	Arguments for this operation. With none, it describes what you already have.

Output Schema

Name	Required	Description
`rows`	Yes	The answers, one object per row, keyed by the column names above. An empty array means the question was understood and nothing matched, which is an answer and not a failure.
`columns`	Yes	The column names, in order. Every row object has exactly these keys, so this is the row shape and reading it is cheaper than inspecting a row.
`statistics`	No	What the query cost.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is supplied. The description does add genuinely useful context beyond them: the auth requirement (linked Whisper account via OAuth or X-API-Key header). However, it never says what a disconnect actually changes, whether it is reversible, or what happens to the existing link — the central behavioral question.

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

Conciseness3/5

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

The auth requirement is stated twice ('Requires your Whisper API key' and 'your API key in the X-API-Key header'), and two separate invocation examples are given without clarifying the relationship between them. The front-loaded CALL template pushes the actual purpose into the background. It is not bloated enough to be harmful, but sentences do not all earn their place.

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?

An output schema exists, so return values need not be explained, and the parameters are covered by the schema. What remains missing is the one thing the schema cannot supply: what the disconnect operation does to the target and whether it can be undone. For a state-changing operation on a control plane, that gap keeps it at minimum-viable rather than complete.

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 description coverage is 100% and the single 'input' object is documented in the schema, so the baseline of 3 applies. The description only adds the no-argument fallback behavior, which is already echoed in the schema's own description of 'input'. No argument structure or expected keys for a disconnect are conveyed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the verb ('disconnect operation') but never states the resource being disconnected — an agent, a session, a linked account, or something else. Compared with siblings like whisper_agents_connect or whisper_agents_revoke, an agent cannot tell from this text which operation applies to which situation. The invocation boilerplate ('served as CALL whisper.agents({op:'disconnect'...})') restates mechanics rather than purpose.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no exclusion against the obvious alternatives (connect, revoke, rename, register). The only conditional statement — 'With no arguments it describes what you already have' — is an odd quirk rather than routing guidance. Calling this instead of whisper_agents_revoke is left entirely to inference.

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

All Whisper tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.