Skip to main content
Glama
Sign In

Whisper

by io.github.whisper-sec
OverviewDiscussionsAdmin

agents: detect

whisper_agents_detect
Read-only

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

Input Schema

NameRequiredDescriptionDefault
inputNoArguments for this operation. With none, it describes what you already have.

Output Schema

NameRequiredDescriptionDefault
rowsYesThe 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.
columnsYesThe 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.
statisticsNoWhat the query cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's real contribution is auth context: an X-API-Key header or a linked OAuth account is required. That is genuinely useful beyond the annotations. However, it discloses nothing about what the operation actually reads or produces, and it offers two inconsistent invocation shapes ({op:'detect', args} vs {skill:'agents.detect', input}), which adds confusion rather than clarity.

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?

Three sentences, none of which explain the operation, with two contradictory call formats and auth restated twice ('Requires your Whisper API key' then 'OAuth or your API key in the X-API-Key header'). The lead sentence burns space on a tautology instead of front-loading what detect does.

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 the central question — what 'detect' examines and why an agent would invoke it — is unanswered. For a zero-required-parameter operation with a nested input object, the description should at minimum state what running with empty input yields and how the result differs from sibling reads like whisper_agents_verify or whisper_agents_trace.

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?

There is only one optional parameter and schema description coverage is 100%, so the baseline of 3 applies. The description's 'args:{...}' and example 'input:{}' suggest the call is typically empty, which is mildly consistent with the schema's 'With none, it describes what you already have,' but it adds no real meaning about the input object's contents.

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 description only restates the tool name: 'the detect operation on the Whisper control plane.' It never says what is being detected (agents? configurations? anomalies?), and with ~40 sibling tools named whisper_agents_*, an agent has no basis to choose this one over agent, list, verify, trace, or policy.

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 guidance and no named alternatives. The only usage-adjacent content is invocation syntax and auth requirements, which are prerequisites rather than selection criteria. The schema hint ('With none, it describes what you already have') is the sole clue about behavior, and it lives in the schema, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Whisper toolsInspect
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.

Resources