Whisper

threatintel

whisper_threatintel

Read-only

Threat-intelligence indicator family (candidate apex/CDN/hosting). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: candidateCdnApex, candidateMultiTenantApex, candidateSharedHostingIp.. Answers without an API key. Example call: {"skill":"threatintel","sub":"candidateCdnApex","input":5}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sub`	Yes	Which sub-verb of this family to run. The example runs "candidateCdnApex".
`input`	Yes	A row limit. The example passes 5.

Output Schema

TableJSON 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.

Changed1 schema field changedSep 25, 2026

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"
+}

First observedSep 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already mark the tool read-only, open-world, and non-destructive; the description adds useful behavioral context by disclosing that no API key is required and that the tool is a family dispatcher that needs a 'sub' verb. No statement contradicts the annotations.

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?

The description is compact and front-loaded, with a clear example sentence. The phrasing 'A family verb: name the sub-verb as "sub" alongside the input' is slightly awkward and the trailing dots after sub-verbs are sloppy, but overall every sentence contributes.

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 two-parameter family dispatcher with an output schema and helpful annotations, the description covers auth requirements, example invocation, and the sub-verb mechanism. It does not exhaustively document every possible sub-verb or the semantics of the returned indicators, but the provided information is sufficient for a basic call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds value by enumerating actual sub-verb values and giving a full example call with input=5. This partially compensates for the lack of enum constraints on 'sub'.

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

Purpose4/5

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

The description clearly identifies this as a threat-intelligence indicator family and lists concrete sub-verbs (candidateCdnApex, candidateMultiTenantApex, candidateSharedHostingIp), making it distinguishable from the sibling whisper_* tools. It is slightly less crisp than a single-action tool because the actual operation is selected via 'sub', but the family and example call make the scope clear.

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 intended use is implied by the threat-intelligence indicator family label and sub-verbs, but there is no explicit when-to-use guidance or comparison to sibling tools. The note 'Answers without an API key' gives one access condition, but not when to choose this tool over alternatives.

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

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.