Skip to main content
Glama

Whisper

by io.github.whisper-sec
OverviewDiscussionsAdmin

psl

whisper_psl
Read-only

Public-suffix-list family (tld-plus-one, is-public-suffix, affiliation). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: tldPlusOne, isPublicSuffix, affiliation.. Answers without an API key. Example call: {"skill":"psl","sub":"tldPlusOne","input":"a.b.example.co.uk"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subYesWhich sub-verb of this family to run. The example runs "tldPlusOne".
inputYesThe indicator to look up: a domain, an IP address, an ASN or a file hash. The example passes a.b.example.co.uk.

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.5/5.0
Behavior3/5

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

Annotations already cover the read-only, open-world, non-destructive profile, so the bar for extra disclosure is lower. The description adds the genuinely useful fact that it answers without an API key, but it does not mention input validation, error behavior, or rate limits, leaving transparency average.

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 description is short and front-loaded with the family identity and an example. It contains redundancy: the sub-verbs are listed in the first sentence and again in the third sentence, and there is a stray double period in 'affiliation..'.

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?

With two fully described required parameters, an output schema, and annotations covering safety, an agent has what it needs to construct a valid call. The description provides the missing accepted sub-verb values and a concrete example; a fuller definition of each sub-verb's return semantics is not necessary given the output schema.

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%, warranting a baseline of 3, but the description adds real value by listing the accepted sub-verb values and giving a full example call that maps "sub" and "input" to concrete values. Without enums in the schema, this list is important for correct invocation.

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 names the tool as a public-suffix-list family and enumerates its sub-verbs (tldPlusOne, isPublicSuffix, affiliation), so an agent can tell it apart from unrelated siblings like whisper_rdap or whisper_origins. It is clear and specific, though it does not explain what each sub-verb computes.

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?

It gives explicit call construction guidance ('name the sub-verb as "sub" alongside the input') and a concrete example, making the mechanics of use clear. However, it never states when to prefer this family over alternatives or when not to use it; the usage context is implied rather than explicit.

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