Skip to main content
Glama
Sign In

Whisper

by io.github.whisper-sec
OverviewDiscussionsAdmin

agents: lookups

whisper_agents_lookups
Read-only

The lookups operation on the Whisper control plane, served as CALL whisper.agents({op:'lookups', 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.lookups","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_lookups"
  }
}

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.6/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 safety is covered. The description adds real context beyond that: authentication via X-API-Key header or a linked Whisper account, and the fact that a zero-arg call returns a description of current state rather than an error. It says nothing about rate limits, result scope, or whether the 'lookup' hits live infrastructure.

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 no-arguments behavior is stated twice (once in prose, once implicitly via 'the example below runs as published'), and the transport/auth preamble is repeated at the end. The call-syntax 'CALL whisper.agents({op:...})' and the JSON example consume most of the text without conveying what the tool 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 explained, but the core question an agent must answer, 'what does a lookups call give me that list/identity/agent do not', is left open. For a zero-required-param tool in a 40-sibling family, the description should carry that differentiation and does not.

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% with a single optional 'input' object, so the baseline is 3. The description's 'with no arguments it describes what you already have' duplicates the schema field description almost verbatim and adds no format, shape, or constraint information beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the operation and domain ('the lookups operation on the Whisper control plane') and says a no-argument call 'describes what you already have', which gives some hint of an introspection-style read. But it never says concretely what a lookup returns or what it looks up, and it does not distinguish itself from close siblings such as whisper_agents_list, whisper_agents_agent or whisper_agents_identity. 'Lookups' essentially restates the 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?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives, despite many overlapping siblings. The only actionable conditions given are prerequisites (API key or linked OAuth account), not selection criteria.

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