Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

get_node

Read-only

Retrieve a node's properties and USES relationships by CMID from a selected database to inspect category structure and dependencies.

Instructions

Get a node's properties and USES relationships by CMID.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmidYes
databaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral detail by saying it returns properties and USES relationships. However, it does not mention error behavior if the node does not exist, database scoping, or whether the result includes other relationship types.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It states the resource, return content, and lookup key efficiently.

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?

This is a simple read tool with two required parameters and no output schema. The description is too terse for that context: it never explains the 'database' parameter, and it does not clarify what 'USES relationships' includes or how missing nodes are handled. An agent can guess the intent, but key calling details are missing.

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%, so the description must compensate. It gives meaning to 'cmid' as the lookup identifier, but the required 'database' parameter is completely unexplained; it is unclear whether it is a database name, identifier, or scope. This is only partial compensation 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?

The description uses a specific verb and resource: 'Get a node's properties and USES relationships.' It also states the lookup key is CMID. It is clear what the tool does, but it does not explicitly distinguish it from the similarly named sibling get_node_page, so it falls 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 when-to-use guidance, no mention of when not to use it, and no explicit alternative such as get_node_page or list_domains. The description leaves the agent to infer the appropriate context entirely.

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