Whisper

agents: agent

whisper_agents_agent

Read-only

The agent operation on the Whisper control plane, served as CALL whisper.agents({op:'agent', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}. Add include:'tombstones' to read an agent that is gone: its newest lifecycle row says whether it was revoked, released, erased or reaped, when, by whom and why. Example call: {"skill":"agents.agent","input":{"agent":"agent-a1f4c0b2d3e4f5a67"}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.

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": {
      "input": "<input>"
    },
    "name": "whisper_agents_agent"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	Arguments for this operation, as an object. The example passes {"agent":"agent-a1f4c0b2d3e4f5a67"}.

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

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, while the description adds useful context about API key/OAuth auth and tombstone lifecycle details such as revocation, release, erasure, reaping, actor, and reason. No annotation contradiction is present.

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 description is generally front-loaded and useful, but it repeats authentication requirements twice ("Requires your Whisper API key" and "Needs a linked Whisper account... or your API key in the X-API-Key header"). The example and tombstone guidance earn their place, but the duplication reduces efficiency.

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?

With an output schema present, the description need not explain return values, and it covers auth, agent identification, listing, and tombstone reads adequately for a read-only agent lookup. It is reasonably complete for the tool's complexity, though nested argument details remain example-driven.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The top-level schema only defines a generic input object, so the description adds significant meaning by showing an example with the agent identifier and by documenting include:'tombstones'. It still does not exhaustively define the possible nested args beyond the example and tombstone option.

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 identifies this as the "agent operation" on the Whisper control plane and clarifies it reads a specific agent, including gone agents via tombstones. It distinguishes itself from listing by directing users to the "agents.list" skill, though the verb is somewhat implicit rather than stated as "retrieve agent".

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?

It tells the caller to list agents with "agents.list" and {"kind":"agents"}, and to add include:'tombstones' when reading an agent that is gone. It also states authentication requirements, but it does not fully explain when to use this versus other agent siblings such as history or trace.

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.