Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

list_subdomains

Read-only

Retrieves public subdomains from a specified CatMapper database so you can review available subdomains for that database.

Instructions

List public subdomains in a CatMapper database.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "database": "<database>"
    },
    "name": "list_subdomains"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — only *public* subdomains are returned — but says nothing about what happens with an unknown database or whether an empty list is a valid outcome.

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?

A single short sentence with no redundant wording, and the key qualifier ('public') is front-loaded. Its brevity comes at the cost of under-specification rather than padding, so it loses only modestly here.

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

Completeness2/5

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

For a simple one-parameter tool this could be close to adequate, but with 0% schema coverage and no output schema, the definition leaves the database parameter format and the shape of results entirely unexplained. An agent knows the intent but not enough to call it confidently with a correct identifier.

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?

With one required parameter at 0% schema description coverage, the description must carry the burden of explaining what 'database' means (an identifier, name, or path?) and it does not. It only implies that a CatMapper database is the target, which is marginal value beyond the bare schema property name.

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?

States a specific verb and resource ('List public subdomains') plus a scoping qualifier ('public') and the data source ('CatMapper database'). It is distinguishable from most siblings by name, but it never explicitly contrasts itself with list_domains, which an agent could reasonably confuse with subdomain listing.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus list_domains or other list tools, no mention of prerequisites such as the database existing, and no note about result limits or pagination. Usage is only implied by the verb 'List'.

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