Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

list_datasets

Read-only

Retrieve all datasets from a specified CatMapper database to identify available data sources for category mapping and metadata inspection.

Instructions

List datasets in a CatMapper database.

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

Input Schema

NameRequiredDescriptionDefault
databaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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. The description adds no behavior beyond that: no indication of whether results are paginated or complete, whether an empty result is possible, or what permissions the database requires.

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?

One sentence, front-loaded with the verb and resource, with no filler or redundant restatement of the title. It is efficient but so terse that it omits information an agent needs, which reads as under-specification rather than disciplined brevity.

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?

For a single-parameter read tool with no output schema, the description plus annotations cover the minimum needed to attempt a call. The unresolved gap is the format of the required "database" argument, which an agent must guess at.

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 the single required parameter, so the description must explain what "database" expects. It only echoes the word ("in a CatMapper database") and never clarifies whether that is a name, slug, ID, or path.

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 ("List datasets") plus a scoping context ("in a CatMapper database"), which is enough to separate it from get_dataset and the other list_* readers. It stops short of explicitly contrasting itself with siblings, so it lands just below the top score.

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 exclusion, and no pointer to an alternative among the many siblings (list_domains, list_properties, get_dataset, search_categories). The use case is inferable from the name alone, but the description contributes nothing to that inference.

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