Skip to main content
Glama

DaedalMap Disaster and Geospatial Data

by com.daedalmap

Read Geometry Catalog

read_geometry_catalog
Read-only

Free geography discovery. Reads the published DaedalMap geometry catalog projection by default, excluding staged and candidate work. Use view='capabilities' first for the global baseline and enhanced countries; use focused inventory views for families, banks, crosswalk products, and named objects. A local loopback MCP may set read_wip=true for internal review. No payment required. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoCatalog view to return. Use capabilities for the concise first-user coverage model. Default summary for compatibility.
limitNoMaximum named reference objects to return. Default 50.
read_wipNoLocal loopback MCP only. When true, reads the internal geometry catalog projection, including staged and in-progress records. Hosted/public MCP requests are denied. Default false.
request_idNoOptional caller-supplied request id for tracing.
country_scopeNoOptional ISO3 country code for view='capabilities'. Returns the selected country's baseline, active depth, families, and query guidance.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "capabilities",
-  "summary",
-  "countries",
-  "admin_coverage",
-  "bridges",
-  "products",
-  "named_reference_objects",
-  "full"
-]New value: +[
+  "capabilities",
+  "summary",
+  "countries",
+  "admin_coverage",
+  "crosswalk_artifacts",
+  "crosswalks",
+  "products",
+  "named_reference_objects",
+  "full"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / country_scope
      Added value: +{
+  "description": "Optional ISO3 country code for view='capabilities'. Returns the selected country's baseline, active depth, families, and query guidance.",
+  "type": "string"
+}
    • addedInput schema / properties / read_wip
      Added value: +{
+  "description": "Local loopback MCP only. When true, reads the internal geometry catalog projection, including staged and in-progress records. Hosted/public MCP requests are denied. Default false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "capabilities",
-  "summary",
-  "admin_coverage",
-  "bridges",
-  "products",
-  "named_reference_objects",
-  "full"
-]New value: +[
+  "capabilities",
+  "summary",
+  "countries",
+  "admin_coverage",
+  "bridges",
+  "products",
+  "named_reference_objects",
+  "full"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / view / description
      Previous value: -"Catalog view to return. Default summary."New value: +"Catalog view to return. Use capabilities for the concise first-user coverage model. Default summary for compatibility."
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "summary",
-  "admin_coverage",
-  "bridges",
-  "products",
-  "named_reference_objects",
-  "full"
-]New value: +[
+  "capabilities",
+  "summary",
+  "admin_coverage",
+  "bridges",
+  "products",
+  "named_reference_objects",
+  "full"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum named geometries to return when view='named_geometries'. Default 50."New value: +"Maximum named reference objects to return. Default 50."
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "summary",
-  "admin_coverage",
-  "bridges",
-  "packages",
-  "named_geometries",
-  "full"
-]New value: +[
+  "summary",
+  "admin_coverage",
+  "bridges",
+  "products",
+  "named_reference_objects",
+  "full"
+]
  5. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description aligns with that, adding that it is read-only and free. It discloses the default behavior (excluding staged/candidate work) and the read_wip restriction (denied for hosted/public). This is useful context beyond the annotation, though it doesn't describe error behavior or response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately long, with a clear opening sentence and useful guidance. However, the 'Current catalog' paragraph includes promotional details (e.g., 'The same geography tools work worldwide...') that are not essential for invocation and could be trimmed. The information is front-loaded reasonably well.

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 the tool is read-only and has no output schema, the description provides sufficient context for an agent to invoke it correctly: it explains the default scope, available view categories, the read_wip limitation, and examples of enhanced country coverage. It doesn't specify exact output format, but for a catalog listing that may be acceptable. The limit parameter is mentioned in schema, and the description gives enough to call it.

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?

Schema coverage is 100%, so the parameter semantics baseline is 3. The description adds value by explaining the intended order of views (capabilities first), the purpose of read_wip, and implicitly linking country_scope to the capabilities view. It does not redefine parameter types, but it gives usage guidance that the schema does not fully convey.

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 the tool reads the published DaedalMap geometry catalog projection by default, excluding staged and candidate work. It distinguishes from geometry-specific operations by emphasizing 'discovery' and 'catalog', though it does not explicitly name sibling alternatives like get_geometry or get_catalog. The purpose is specific and actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage strategy: 'Use view='capabilities' first for the global baseline and enhanced countries; use focused inventory views for families, banks, crosswalk products, and named objects.' It also gives a constraint (read_wip only for local loopback MCP) and notes no payment required. It does not explicitly mention when to choose this over siblings, but the intended selection criteria are clear.

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

All DaedalMap Disaster and Geospatial Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct scopes with detailed 'Use this' guidance, but a few pairs like get_disaster_link_chain and get_disaster_links_for_event, or query_dataset versus the specialized get_* event tools, could cause momentary confusion. Overall, descriptions mitigate overlap well.

Naming Consistency4/5

The majority follow a consistent verb_noun pattern (check_, compare_, convert_, create_, estimate_, get_, list_, resolve_). Minor exceptions like loc_id_info and query_dataset are acceptable but break the pattern slightly.

Tool Count3/5

28 tools exceed the preferred range, but the broad domain spanning disasters, geospatial geometry, reference conversion, and export jobs justifies many of them. Still, the count feels heavy and might overwhelm agents.

Completeness5/5

The tool surface is remarkably comprehensive: discovery (catalog, pack, geometry catalog), resolution (point, reference, scope), geometry (check, get, compare), conversion (quote, create, status), and disaster events for multiple types. No critical dead ends for the stated domain.

Resources