Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

list_properties

Read-only

Retrieve metadata properties from a CatMapper database to inspect schema and available fields for data integration.

Instructions

List metadata properties 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_properties"
  }
}

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 safety is covered. The description adds essentially nothing beyond the purpose statement: no note on result volume, pagination, ordering, or what happens when the database contains no properties.

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 short, front-loaded sentence with no filler or repetition. It is efficient, though its brevity contributes to the documentation gaps noted elsewhere.

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?

This is a low-complexity, single-parameter listing tool, and the annotations plus schema cover the call structure. However, with no output schema there is nothing describing the shape of the returned property list, and the database argument's expected format remains undefined.

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 coverage is 0% for the single required 'database' parameter, so the description carries the burden of explaining it. 'in a CatMapper database' only gestures at the parameter's role; it never says whether a database is a name, an ID, or a path, which is exactly what an agent needs before calling.

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 names a specific verb (List) and resource (metadata properties) scoped to a CatMapper database, which is unambiguous on its own. It does not distinguish itself from the other list_* siblings (list_datasets, list_domains, list_subdomains), so it falls short of a 5.

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 exclusions, and no mention of alternatives such as list_datasets or get_dataset. An agent must infer from the name alone when this listing is the right call versus another list_* or get_* tool.

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