Whisper

agents: verify

whisper_agents_verify

The verify operation on the Whisper control plane, served as CALL whisper.agents({op:'verify', args:{...}}). Requires your Whisper API key. Example call: {"skill":"agents.verify","input":{"name":"example.com"}} 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_verify"
  }
}

Input Schema

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

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

Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the description's main added value is the auth requirements (OAuth link or X-API-Key header), which is genuinely useful. However, it never explains what state the non-read-only, open-world verification touches or what happens on failure, leaving the mutation profile opaque.

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

Conciseness2/5

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

The text is repetitive and disorganized: authentication is stated twice ("Requires your Whisper API key" and "or your API key in the X-API-Key header"), and two different invocation syntaxes are presented (CALL whisper.agents({op:'verify'...}) and {"skill":"agents.verify",...}) without explaining the relationship, which is likely to confuse rather than clarify.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 the single parameter is schema-documented. But for an open-world, non-read-only verification operation with many similar siblings, the description omits the two things only prose can supply: what verification actually does and when to pick this tool.

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?

With 100% schema coverage and a single nested input object, the schema already carries the burden. The description reinforces this with a concrete example payload {"name":"example.com"}, which confirms the expected shape of the nested input, though it adds no field-level meaning beyond the schema.

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 verify operation on the Whisper control plane" essentially restates the tool name/title without saying what is being verified, what the outcome means, or how it differs from the sibling whisper_verify or whisper_agents_domain. The only concrete signal is the example input {"name":"example.com"}, which hints at domain verification but is never stated.

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?

The description gives authentication conditions (linked OAuth account or X-API-Key header) but no guidance on when to use this versus whisper_verify, whisper_agents_domain, or other agents.* siblings. An agent has no basis for choosing among near-identical verify-related tools.

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.