Get Catalog
get_catalogRead-only
Free discovery. Returns the list of live agent-ready data packs available on DaedalMap.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DaedalMap World Development Indicators
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, so description is not required to restate it. The description adds no behavioral traits beyond annotations; 'Free discovery' is marketing fluff.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise with two short sentences. No unnecessary words except possibly 'Free discovery', but overall efficient and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description adequately communicates the return value. Lacks details on pagination or limits, but for a simple listing tool it suffices.
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?
No parameters exist, and schema coverage is 100%. Baseline score of 4 is appropriate as description does not need to add parameter details.
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 clearly states it returns a list of data packs on DaedalMap, using specific verb 'returns' and resource 'live agent-ready data packs'. However, it does not explicitly differentiate from siblings like get_pack or query_dataset, though the scope is implied.
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?
No guidance on when to use this tool versus alternatives such as get_pack or query_dataset. The description lacks context for selection.
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.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool has a clearly distinct role: get_catalog lists available packs, get_pack provides detailed metadata for one pack, get_tool_help offers guidance on other tools, and query_dataset executes data queries. No overlap or ambiguity between them.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (get_catalog, get_pack, get_tool_help, query_dataset) with snake_case and a clear verb prefix. This is predictable and uniform.
Tool Count5/5
Four tools is a well-scoped set for a data access server: two for discovery (catalog and pack metadata), one for meta-guidance, and one for querying. This is within the ideal 3-15 range and each tool earns its place.
Completeness5/5
The surface covers the full lifecycle of a data access workflow: discover (get_catalog), understand (get_pack), learn to use (get_tool_help), and query (query_dataset). There are no obvious missing operations for a read-only data server.