Whisper

agents: partner

whisper_agents_partner

The partner operation on the Whisper control plane, served as CALL whisper.agents({op:'partner', args:{...}}). Requires your Whisper API key. It is gated on partner authority rather than on arguments: without it the call is refused whatever you pass. Example call: {"skill":"agents.partner","input":{}} Needs a linked Whisper account (OAuth) or your API key in the X-API-Key header.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "whisper_agents_partner"
  }
}

Input Schema

Name	Required	Description	Default
`input`	No	Arguments for this operation. With none, it describes what you already have.

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

Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=true, and the description usefully adds beyond them: authentication (API key in X-API-Key or linked OAuth account) and an authority gate that refuses the call regardless of arguments. That refusal-on-authority behavior is genuinely non-obvious and valuable. It still does not disclose what state the operation changes, despite readOnlyHint being false, leaving the mutation's effect unexplained.

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

Conciseness4/5

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

Kept to a few sentences, with the authority gate and auth requirement stated up front and an example call included. Minor waste: the API key requirement is stated twice ('Requires your Whisper API key' and 'your API key in the X-API-Key header'), and two different invocation formats (CALL syntax vs. {skill, input} JSON) are shown, which could 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 needn't be explained, and auth/gating is covered. But the single most important fact — what the 'partner' operation does — is absent, which for a non-read-only, open-world operation leaves the agent unable to judge whether to call it at all.

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?

Only one optional nested parameter exists and schema coverage is 100%, so baseline is 3. The description's note that an empty call 'describes what you already have' roughly duplicates the schema's own 'With none, it describes what you already have' text, adding no new meaning about the args object's shape.

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 partner operation" restates the tool name without saying what the operation actually does — no verb describing an action or outcome. The description only tells the agent how to invoke it (CALL whisper.agents({op:'partner'})) and what gates it, which is invocation mechanics rather than purpose. An agent cannot tell from this text what 'partner' means or returns.

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 a partial hint that calling with no input 'describes what you already have,' which implies a read-like usage mode, but no guidance on when to choose this over the 20+ sibling operation tools (agent, connect, register, token, etc.). No prerequisites, sequencing, or exclusions are stated.

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.