Skip to main content
Glama
Sign In

Whisper

by io.github.whisper-sec
OverviewDiscussionsAdmin

agents: identity

whisper_agents_identity
Read-only

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

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

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely new context: authentication requires a linked Whisper account via OAuth or an API key in the X-API-Key header. That auth requirement is the kind of operational detail annotations do not carry, and nothing in the text contradicts the read-only annotation.

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

Conciseness3/5

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

The auth requirement is front-loaded reasonably well, but the 'with no arguments it describes what you already have' idea is stated twice and two separate invocation forms (the CALL syntax and the JSON example) are given for a zero-argument call. It is not bloated to the point of confusion, but several clauses do not earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, and auth plus invocation shape are covered. However, for a tool whose entire purpose is introspection of existing identity, the description never clarifies what 'what you already have' actually encompasses, leaving the agent to guess at scope.

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% and the single nested 'input' object is already documented as optional. The description reinforces that an empty input is meaningful rather than an error, which is a small value-add over the schema, but it supplies no argument syntax or examples of non-empty inputs. Baseline 3 applies.

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 resource ('identity operation on the Whisper control plane') and hints at effect ('with no arguments it describes what you already have'), but never states concretely what identity data is returned or how it differs from nearby siblings such as whisper_identify or whisper_agents_token. An agent gets the general area but not the specific outcome.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The only implied guidance is the note that an empty argument set returns existing state, which is invocation mechanics rather than selection guidance.

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