Whisper

agents: domain

whisper_agents_domain

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

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

Behavior2/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 description should explain what state changes. Instead it discloses only auth mechanics and calling convention, leaving the actual effect of this mutating call entirely unspecified. The auth/OAuth and X-API-Key detail is genuine value beyond the annotations, which keeps this above a 1, but the core behavioral disclosure is missing.

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 content is not front-loaded with purpose; it opens with an internal calling convention ('CALL whisper.agents({op:'domain', args:{...}})') that duplicates the MCP invocation the agent is already making. Authentication is stated twice ("Requires your Whisper API key" and again as the X-API-Key header), and two overlapping example payloads are given in different formats.

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. But for a non-read-only, open-world operation with ~40 look-alike siblings, the definition never says what the operation does or when to pick it, which leaves an agent unable to invoke it correctly beyond guessing at the example payload.

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?

The schema has 100% description coverage, though the sole parameter's description is a generic 'Arguments for this operation' wrapper. The description does add a concrete example ({"name":"example.com"}), which tells the agent one plausible key, but it does not enumerate or explain the allowed argument set. Baseline 3 applies given high schema coverage plus marginal example value.

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 domain operation on the Whisper control plane" restates the title (agents: domain) rather than stating what the operation actually does. An agent cannot tell from this whether it registers, inspects, assigns, or deletes a domain, nor how it differs from siblings like whisper_agents_host, whisper_agents_resolver, or whisper_agents_register. Only the example payload ('name':'example.com') hints that it acts on a domain name.

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 when-to-use or when-not-to-use guidance is given, and no sibling is named as an alternative even though there are ~40 siblings including several domain-adjacent ones. The only conditional content is authentication ('linked Whisper account (OAuth) or your API key'), which is a prerequisite, not usage guidance.

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.