Skip to main content
Glama

Data catalogue

get_data_catalogue
Read-onlyIdempotent

The datasets this workspace can ground a plan in — sources, row counts, and the facts the agents are briefed with.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_data_catalogue"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint, so safety is covered structurally. The description does add useful content context — it says the response contains dataset sources, row counts, and agent briefing facts — but says nothing about catalogue size, whether it spans all sources, or how results are scoped to the workspace beyond a passing mention.

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 sentence with no filler, and the core noun 'datasets' is front-loaded. The em-dash aside is slightly cryptic in wording ('the facts the agents are briefed with') but costs little space.

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?

With no output schema, no parameters, and only read-only annotations, the description carries the burden of explaining what comes back. It names three content categories but does not describe the structure, granularity, or size of the catalogue, leaving the agent partially informed.

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

Parameters4/5

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

The tool takes zero parameters, and the schema accepts additional properties, so there is no parameter semantics for the description to compensate for. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment describes the content ('sources, row counts, and the facts the agents are briefed with') but never states an action verb or scope explicitly — an agent must infer it is a read-only catalogue listing for the current workspace. It also gives no differentiation from siblings such as get_content_assets or get_page_summary, which could plausibly overlap.

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 precondition, and no mention of an alternative tool. The phrase 'can ground a plan in' hints at a planning context but leaves the agent to guess the trigger condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources