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 CIA World Factbook
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds context beyond the readOnlyHint annotation by describing the tool as 'Free discovery' and specifying the source (DaedalMap), though it does not disclose additional behavioral details.
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?
Single sentence efficiently conveys purpose and scope with zero wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/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, description fully covers the tool's behavior: returns a list of available data packs.
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; description adds no parameter info, but baseline for zero-param tools is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool returns the list of live agent-ready data packs available on DaedalMap, distinguishing it from siblings like get_pack (retrieving a specific pack) and query_dataset (querying within a pack).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or alternatives, but context implies it's a discovery tool to be used before accessing specific packs or datasets.
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/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: catalog lists available packs, pack provides detail on a specific pack, tool_help explains tool usage, and query_dataset executes data queries. There is no overlap that could cause misselection.
Naming Consistency5/5
Names follow a consistent verb_noun pattern: get_catalog, get_pack, get_tool_help, and query_dataset all use action nouns. Though one uses 'query' instead of 'get', the pattern is uniform and predictable.
Tool Count5/5
With only 4 tools, the set is tightly scoped for a data access facade: discovery, metadata, help, and query. This is well within the ideal range and each tool earns its place for the server's purpose.
Completeness5/5
The tool surface fully covers the domain: users can discover packs, inspect a pack's metadata, get guidance on tools, and run queries. For a read-only data server, there are no missing operations or dead ends.