Whisper

agents: alert

whisper_agents_alert

The alert operation on the Whisper control plane, served as CALL whisper.agents({op:'alert', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published. Example call: {"skill":"agents.alert","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_alert"
  }
}

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 declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds genuinely non-annotated context — API key or OAuth linkage plus the X-API-Key header requirement. It also discloses the no-argument introspection behavior. It stops short of describing what happens when arguments are supplied, so for a non-read-only, open-world operation the behavioral picture is only half drawn.

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?

Short and front-loaded with the operation identity, and the example is placed sensibly. There is mild redundancy: the API key requirement appears twice ("Requires your Whisper API key" and again as the OAuth/X-API-Key sentence) along with metatext about "the example below runs as published."

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. However, for a 1-parameter, nested-object, open-world mutation-capable tool, the description never establishes what the operation is for or what arguments it accepts, which is the core information an agent needs before invoking 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% for the single `input` object, so the baseline is 3. The description adds the invocation form (`CALL whisper.agents({op:'alert', args:{...}})` and the example payload) but never indicates which keys belong inside `args`, leaving the actual argument vocabulary undocumented in both schema and description.

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 alert operation on the Whisper control plane" essentially restates the tool name and title without saying what alerting actually does — configure a rule, list existing alerts, send a notification? Nothing distinguishes it from siblings such as whisper_agents_policy, whisper_agents_logs, or whisper_agents_watch, which plausibly overlap with alerting semantics.

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 only usage statement is the zero-argument case ("With no arguments it describes what you already have"), which usefully signals an introspection mode. There is no guidance on when to use this operation versus the many sibling operations, nor on what conditions would call for passing arguments.

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.