Public Suffix List

Public Suffix

public_suffix

Read-onlyIdempotent

Just the public suffix.

Input Schema

Name	Required	Description	Default
`domain`	Yes

Output Schema

Name	Required	Description	Default
`input`	Yes	Canonical form of the input domain
`public_suffix`	Yes	Public suffix part of the domain

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "domain": "www.example.com"
+  },
+  {
+    "domain": "github.io"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "input": {
+      "description": "Canonical form of the input domain",
+      "type": "string"
+    },
+    "public_suffix": {
+      "description": "Public suffix part of the domain",
+      "type": "string"
+    }
+  },
+  "required": [
+    "input",
+    "public_suffix"
+  ],
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

D1.1/5.0

Behavior1/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds no behavioral details (e.g., what constitutes a public suffix, edge cases like TLDs).

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

Conciseness2/5

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

The description is extremely short, but this is under-specification, not efficiency. It lacks essential information for a 4-word description to be helpful.

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

Completeness1/5

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

Given a single parameter and an output schema (not shown), the description still fails to explain the tool's return type or behavior. It is completely inadequate for an AI agent to understand its purpose.

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

Parameters1/5

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

Schema has 0% description coverage and the description offers no additional meaning for the single 'domain' parameter. The examples in the schema are the only clues, but the description itself adds nothing.

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

Purpose1/5

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

Description 'Just the public suffix' is a tautology that restates the tool name without specifying what the tool does. It does not indicate the action (e.g., extract or return) nor clarify the resource, making it nearly meaningless.

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

Usage Guidelines1/5

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

No guidance provided. The description fails to distinguish this tool from the sibling 'registrable_domain' or any alternatives, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Public Suffix List tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.