Whisper

agents: host

whisper_agents_host

The host operation on the Whisper control plane, served as CALL whisper.agents({op:'host', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.host","input":{"name":"my-host","type":"TXT","value":"hello"}} 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_host"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	Arguments for this operation, as an object. The example passes {"name":"my-host","type":"TXT","value":"hello"}.

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.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is partly covered. The description adds genuine value by stating the authentication requirement (API key or OAuth) and the invocation form, but it never explains what state 'host' creates or mutates, whether the operation is idempotent, or what side effects follow.

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 text is short but fragmented: it mixes two incompatible invocation notations (CALL whisper.agents({op:'host', args:{...}}) and {"skill":"agents.host",...}) and repeats the credential requirement twice (API key sentence and X-API-Key header sentence). The intent is not front-loaded with what the tool actually does.

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?

An output schema exists, so return values need not be described, and auth requirements are covered. However, for a non-read-only write-type operation with nested input, the description still leaves the core effect of 'host' undefined, which is the one thing an agent most needs before calling it.

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 there is only one 'input' object parameter, so the baseline is 3. The description's example object {"name":"my-host","type":"TXT","value":"hello"} does add a little meaning about plausible inner fields, but it is presented as an illustrative snippet rather than documented semantics, so it barely exceeds what the schema already provides.

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

Purpose2/5

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

The description says 'The host operation on the Whisper control plane', which essentially restates the tool name ('agents: host') without explaining what hosting means here or what resource is affected. The example payload ({name, type, value} with type TXT) hints at some record/entity creation, but the agent must infer it; nothing distinguishes this from the 22 sibling agents_* operations.

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?

No guidance on when to use this tool versus siblings like whisper_agents_register, whisper_agents_agent, or whisper_agents_list. The only conditional content is about credentials (linked OAuth account or X-API-Key header), which is a prerequisite, not a usage rule.

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.