Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

get_node_page

Read-only

Retrieve the explore-page representation for a CatMapper node by specifying its database and cmid, so you can inspect node details and context.

Instructions

Get the explore-page representation of a CatMapper node.

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>",
      "cmid": "<cmid>"
    },
    "name": "get_node_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmidYes
databaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds only that the return is a page-shaped representation rather than raw node data, but it does not explain what that representation contains, how it differs from get_node's output, or any failure behavior for unknown cmid/database.

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?

A single front-loaded sentence with no filler, but it is under-specified rather than truly concise; the length budget is spent on a phrase ("explore-page representation") that conveys little.

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 two-required-parameter retrieval tool with no output schema, no parameter docs and undefined domain vocabulary, the description leaves too much unresolved: what a node page returns, what database means, and when to prefer get_node instead.

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% for two required parameters (cmid, database), so the schema provides names and types only. The description never mentions either parameter, leaving the agent to guess that cmid identifies a CatMapper node and database scopes the lookup.

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

Purpose3/5

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

The description names a verb ("Get") and a resource ("the explore-page representation of a CatMapper node"), but "explore-page representation" is undefined jargon and the definition never distinguishes this from the sibling get_node, which an agent would naturally consider equivalent. Purpose is discernible but not disambiguated.

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 get_node or any other sibling, and no stated prerequisites. The agent must infer usage purely from the name.

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