Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

get_dataset

Read-only

Retrieve dataset details and category data from a specified database using its CMID; optionally filter by domain and include child categories.

Instructions

Get a dataset's details and category data; optionally filter by domain.

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

Input Schema

NameRequiredDescriptionDefault
cmidYes
domainNo
childrenNo
databaseYes

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the payload includes category data and that domain filtering is available, but says nothing about what the children flag changes in behavior or how results are shaped.

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?

A single compact sentence with the resource and the optional filter front-loaded, no filler. It is efficient, though its brevity is achieved partly by omitting the parameter detail an agent needs.

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?

For a four-parameter lookup with zero schema descriptions and no output schema, the description leaves too much unspecified — notably what children does and what cmid/database identify. An agent would have to guess at invocation details.

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 four parameters, so the description must carry the burden. It touches only 'domain' and even then gives no format (name vs. ID) or effect on results; cmid, database, and especially the children boolean are completely unexplained.

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?

States a specific verb ("Get") and resource ("a dataset's details and category data"), plus the optional domain filter. It is distinguishable from list_datasets and get_node, but it never explicitly names a sibling or the boundary between them.

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?

The only usage signal is "optionally filter by domain," which hints at a filtering capability but not when to choose this over list_datasets or get_node. No prerequisites, no when-not-to-use, no mention of what cmid or database must reference.

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