Skip to main content
Glama

Whisper

by io.github.whisper-sec
OverviewDiscussionsAdmin

explain

whisper_explain
Read-only

Explain a verdict - the evidence and reasoning behind it. Answers without an API key. Example call: {"skill":"explain","input":"example.com"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes example.com.

Output Schema

TableJSON 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. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "A tabular graph answer: the column names, the rows keyed by them, and the cost.",
+  "properties": {
+    "columns": {
+      "description": "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.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rows": {
+      "description": "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.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "statistics": {
+      "description": "What the query cost.",
+      "properties": {
+        "executionTimeMs": {
+          "description": "Milliseconds the graph spent answering.",
+          "type": "integer"
+        },
+        "rowCount": {
+          "description": "How many rows came back.",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "rowCount"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "columns",
+    "rows"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already communicate readOnly, openWorld, and non-destructive behavior. The description adds the useful fact that it answers without an API key, but otherwise does not disclose additional behaviors such as response shape or limitations. No contradiction with annotations.

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

Conciseness5/5

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

Two short sentences carry a clear definition, a key operational fact, and a concrete example with no filler. The most important phrase is front-loaded.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup tool with a full input schema, output schema, and read-only annotations, the description provides the essential operational context. It could be slightly more explicit about how an indicator maps to a 'verdict', but the example and schema cover that gap well enough.

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?

The input schema fully describes the single parameter, including the accepted value types (domain, IP, ASN, file hash), so schema coverage is 100%. The description's example adds a concrete illustration but does not go beyond what the schema already states.

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

Purpose5/5

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

The description states a specific verb ('Explain') and a specific resource ('a verdict - the evidence and reasoning behind it'), which clearly sets it apart from sibling actions like assess or identify. The example call reinforces the intended input.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is appropriate when you need the evidence/reasoning behind a verdict and notes it works without an API key, but it does not explicitly name alternatives or state when not to use it. Context is implied rather than direct.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources