Skip to main content
Glama

Whisper

by io.github.whisper-sec
OverviewDiscussionsAdmin

lookupTorRelay

whisper_lookupTorRelay
Read-only

Look up Tor relay metadata for an address. Answers without an API key. Example call: {"skill":"lookupTorRelay","input":"185.220.101.1"}

Input Schema

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

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. Added
  3. Removed
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

The description adds a concrete behavioral detail beyond the annotations: 'Answers without an API key,' which clarifies authentication expectations. The readOnlyHint, openWorldHint, and destructiveHint annotations already cover safety, and the description does not contradict them.

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?

The description is two tight sentences: the first states the purpose, the second provides authentication context and a concrete example. Every sentence earns its place with no filler or repetition.

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 simple one-parameter lookup tool with an output schema and safety annotations, the description is largely complete. The only notable gap is the mismatch between the description's 'address' and the schema's broader accepted indicator types, which could lead an agent to underuse the tool.

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 input parameter is fully described, so the baseline is 3. The description's example call illustrates the expected JSON format but does not add meaningful semantic detail beyond what the schema already provides.

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 states the action and resource: 'Look up Tor relay metadata for an address.' This distinguishes it from generic lookup tools. However, it says 'address' while the schema supports domains, IPs, ASNs, and file hashes, creating a slight scope mismatch that prevents a 5.

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 for Tor relay lookups and notes that no API key is needed, which gives some usage context. But it provides no explicit guidance about when to choose this tool over its siblings, such as whisper_lookupTlsFingerprint or whisper_identify, nor any exclusions.

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