Whisper

agents: trace

whisper_agents_trace

Read-only

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

Input Schema

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

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

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context by stating the auth requirement (linked Whisper account via OAuth or an X-API-Key header). However, it discloses nothing about what trace actually performs, whether it contacts the target, or how long it takes.

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 API key requirement is stated twice ("Requires your Whisper API key" and "or your API key in the X-API-Key header"), and two mutually inconsistent invocation shapes are given: whisper.agents({op:'trace', args:{...}}) versus {"skill":"agents.trace","input":{...}}. The opening sentence spends the front-loaded position on a restatement of the name rather than the purpose.

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 explained, but for a tool sitting among 22 agents_* siblings with an open-world read hint, the description should say what is being traced and when to pick it. The conflicting call signatures leave the invocation contract ambiguous, which is a real completeness gap for an agent constructing the call.

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% for the single input object, so the baseline is 3. The description's example argument {"dest":"203.0.113.7"} does add a little meaning by showing that a destination address is a valid key, which the schema's generic "Arguments for this operation" does not convey. It stops short of documenting other possible argument keys.

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 trace operation on the Whisper control plane" restates the tool name rather than explaining what tracing does or what resource it acts on. The example argument {"dest":"203.0.113.7"} hints that a destination address is traced, but the agent must infer the actual effect. Nothing distinguishes it from siblings such as whisper_agents_detect, whisper_agents_lookup, or whisper_agents_verify.

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?

There is no when-to-use guidance and no mention of when to prefer this over the many sibling operations (detect, host, resolver, verify, etc.). The description only addresses authentication prerequisites, which is context, not usage selection. An agent has to guess based on the name alone.

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.