Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

translate

Read-only

Converts tabular category data synchronously via CatMapper API to map categories across databases, tables, properties, domains, and keys; returned rows may be logged.

Instructions

Translate tabular category data synchronously. The CatMapper API may log returned rows.

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>",
      "table": "<table>",
      "property": "<property>",
      "domain": "<domain>",
      "key": "<key>"
    },
    "name": "translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
termNo
tableYes
domainYes
contextNo
countryNo
datasetNo
databaseYes
propertyYes
year_endNo
year_startNo
unique_rowsNo
countsamenameNo

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 that execution is synchronous and that returned rows may be logged by CatMapper, which is useful privacy context, but it does not disclose return shape, rate limits, or failure behavior.

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 definition is two front-loaded sentences with no filler; every clause ('synchronously,' 'may log returned rows') carries information. It could be expanded for completeness, but that is a completeness issue rather than wasted wording.

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 complex, 13-parameter external-API tool with no output schema and no parameter descriptions, and the description leaves the return value, auth needs, and error behavior unaddressed. The logging and synchronous notes help, but the definition is far too thin for the tool's complexity.

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

Parameters1/5

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

The schema has 13 parameters with 0% description coverage, including required fields like database, table, property, domain, and key. The description mentions 'tabular category data' but never explains any parameter's meaning or expected format, so it does not compensate for the schema 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 gives a specific verb and resource ('Translate tabular category data') and adds synchronous execution. It does not differentiate this from sibling tools such as search_categories or preview_merge, so it is clear but not routing-grade.

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 translate versus any sibling, nor any preconditions or exclusions. The only usage clue is 'synchronously,' which does not tell an agent when this tool is the right choice.

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