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 Administrative Boundaries (loc_id to polygon)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, so safety is covered. Description adds 'Free discovery' implying no cost/limits and 'live' implying freshness. However, no mention of pagination or output size limits, and no output schema to clarify return structure.
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 with key info front-loaded ('Free discovery'). No fluff.
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?
For a zero-parameter read-only tool, the description provides sufficient context: what is returned and from where. Could mention if the list is exhaustive or paginated, but overall adequate.
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; schema coverage is trivially 100%. Description adds no param info needed.
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 verb (returns) and resource (list of live agent-ready data packs on DaedalMap). Distinguished from siblings: 'get_boundary' suggests boundaries, 'get_pack' suggests single pack, 'loc_id_info' suggests location data.
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 when-not-to-use vs alternatives. 'Free discovery' hints at lightweight use, but lacks formal guidance. Adequate for a simple tool but could be more directive.
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.4/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: discovery (get_catalog, get_pack), geometry retrieval (get_geometry), hierarchy (loc_id_info, resolve_loc_id_scope), relationship analysis (compare_geographies), preflight (check_geometry), export estimation and creation (estimate_geometry_package, create_geometry_export), job status (get_job_status), and help (get_tool_help). Even closely related tools like check_geometry and estimate_geometry_package address different concerns (shape availability vs export artifact), leaving no ambiguity.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (check_geometry, compare_geographies, create_geometry_export, estimate_geometry_package, get_catalog, get_geometry, get_job_status, get_pack, get_tool_help, resolve_loc_id_scope). However, 'loc_id_info' breaks the pattern by being a noun phrase rather than a verb action, causing a minor deviation from the otherwise uniform convention.
Tool Count5/5
With 11 tools, the server covers the key operations for administrative boundary data—discovery, geometry retrieval, hierarchy navigation, comparison, export, and job management—without overreach. Each tool is necessary for a coherent workflow, and the count fits well within the typical 3-15 range for a domain-specific MCP server.
Completeness5/5
The tool set effectively covers the full lifecycle needed for administrative boundary use: discovery (catalog/pack), preflight checks, geometry retrieval, hierarchical navigation, relationship analysis, export estimation/creation, and job status. It includes essential utilities like get_tool_help for onboarding. No obvious gaps exist for the server's purpose; if anything, it is notably thorough for read/export operations.