Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

search_categories

Read-only

Search categories and entities in ArchaMap or SocioMap by term, domain, country, dataset, contexts, and year range to locate matching CMIDs and metadata.

Instructions

Search categories and entities. Database is ArchaMap or SocioMap; contexts and dataset are CMIDs.

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

Input Schema

NameRequiredDescriptionDefault
termNo
limitNo
domainNoCATEGORY
countryNo
datasetNo
contextsNo
databaseYes
propertyNoName
year_endNo
year_startNo
context_modeNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 the safety profile is covered. Beyond that, the description adds only the valid database names and the fact that contexts/dataset values are CMIDs; it says nothing about result size, default limits (limit=100), pagination, or how results are ordered.

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?

Two short sentences with no filler, and the core verb+resource leads. The phrasing is terse to the point of being cryptic ('contexts and dataset are CMIDs') but nothing is redundant.

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?

An 11-parameter, open-world search with no output schema and no per-parameter documentation needs considerably more explanation than two sentences. The description leaves an agent guessing at year-range semantics, context_mode behavior, domain defaults, and what a result record looks like.

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 11 parameters, so the description must compensate and it largely does not. It clarifies only database, contexts, and dataset; term, limit, domain, country, property, year_start, year_end, and context_mode ('all' vs 'any') remain unexplained in both schema and description, which is a serious gap for filter-shaped inputs.

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 opens with a specific verb and resource pair, 'Search categories and entities,' and narrows the universe of data to two named databases (ArchaMap or SocioMap). This lets an agent understand what is being searched, though it does not contrast the tool with siblings such as get_node or list_domains.

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 or when-not-to-use guidance, and no alternative tool is named. The only contextual statements concern value formats for two parameters ('ArchaMap or SocioMap', 'CMIDs'), which is parameter information rather than invocation guidance.

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