Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

list_domains

Read-only

Retrieves all public domains from a specified CatMapper database so you can identify available domains before searching categories or inspecting nodes.

Instructions

List public domains 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_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 meaningful behavioral detail — that only public domains are returned — but says nothing about pagination, result size, or whether an empty database errors or returns an empty list.

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 front-loaded sentence with no filler, which is structurally clean. It is arguably under-sized for a tool whose only parameter is entirely undocumented, but nothing written is wasteful.

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?

With no output schema and no parameter documentation, the description is the only channel for that information and it supplies none of it. An agent knows the tool lists public domains but not what to pass or what shape of data comes back.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter, 'database', is undocumented in both the schema and the description. The agent cannot tell whether it expects a database name, ID, or path, so the description fails to compensate for the coverage gap.

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 (List) and resource (public domains) scoped to a CatMapper database, which lets an agent distinguish it from list_subdomains or list_datasets. It does not explicitly name or contrast the sibling tools, so it stops short of 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 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 tool versus list_subdomains, list_datasets, or search_categories, and no prerequisites or exclusions are stated. The agent must infer that this is the top-level entry point for domain enumeration.

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