Whisper

agents: register

whisper_agents_register

The register operation on the Whisper control plane, served as CALL whisper.agents({op:'register', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.register","input":{"label":"my-first-agent"}} 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_register"
  }
}

Input Schema

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

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 description's main added value is the authentication requirement (X-API-Key header or OAuth link). It omits idempotency behavior, quota/rate limits, and the shape of a registration result, which matters for a non-destructive but mutating call.

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 note, invocation syntax, and example are packed into four somewhat overlapping sentences, and the example call appears twice in substance (once as CALL syntax, once as JSON). Nothing is wasted outright, but it is not front-loaded around the core effect of the tool.

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 no explanation, and auth is covered. For a mutating, open-world registration endpoint referenced alongside 30+ sibling operations, however, the description leaves the agent without the effect, duplicate handling, or prerequisites for the linked account.

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 100% and the single nested 'input' parameter is already described with the same {"label":"my-first-agent"} example the description repeats. The description adds no new semantics about accepted keys inside the args object or their constraints, so it sits at the baseline.

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 operation ('register') and the surface ('Whisper control plane'), and the example label 'my-first-agent' hints that an agent identity is being created. But it never states plainly what registration produces or how it differs from siblings like whisper_agents_agent or whisper_agents_rename, so the agent must infer the effect.

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?

Auth prerequisites are stated (API key or linked OAuth account), but there is no guidance on when to call register versus whisper_agents_list, whisper_agents_agent, or whisper_agents_rename, and no note on what happens if an agent with the same label already exists.

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.