Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

preview_merge

Read-only

Preview a category merge to identify cyclic parent references before committing changes; the merge is not applied.

Instructions

Preview a category merge and identify cyclic parent references. Does not apply the merge.

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>",
      "keep_cmid": "<keep_cmid>",
      "delete_cmid": "<delete_cmid>"
    },
    "name": "preview_merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYes
keep_cmidYes
delete_cmidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so "does not apply the merge" largely restates structured data; the genuinely additive detail is that the preview surfaces cyclic parent references. The description does not say what happens when a cycle is detected (error vs. reported result) or what the preview payload contains, which matters for a read-only diagnostic tool.

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?

Two short sentences with the primary action front-loaded and the boundary condition immediately after. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

The purpose and read-only nature are clear, but with 0% schema coverage, no output schema, and no parameter explanation, an agent still lacks the information needed to construct a correct call confidently. For a three-required-parameter merge preview, the definition should at minimum clarify the cmid parameters and the cycle-detection outcome.

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% across three required parameters (database, keep_cmid, delete_cmid), and the description mentions none of them. The names hint at meaning, but nothing explains whether cmid values are category IDs, what happens if they are in different databases, or how 'keep' vs 'delete' semantics resolve conflicts.

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

Purpose5/5

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

States a specific verb and resource ("Preview a category merge") plus a secondary function ("identify cyclic parent references"), and explicitly closes the scope with "Does not apply the merge." An agent can tell exactly what the tool does and, critically, what it will not do, without inspecting the schema.

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

Usage Guidelines3/5

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

The phrase "Does not apply the merge" implies this is a dry-run step to be used before an actual merge, which is useful implied guidance. However, no alternative tool is named for applying the merge, and there are no explicit conditions for when to prefer or skip this preview.

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