Skip to main content
Glama

DaedalMap Geography Tools (loc_id)

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.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description reinforces a read-only profile. It adds meaningful behavior beyond the annotation: default excludes staged/candidate work, read_wip is only for local loopback MCP, and the catalog delivers deeper administrative tiers where country releases exist. No contradiction with annotations.

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 core operational guidance is front-loaded in the first three sentences, which is good. However, 'Free geography discovery.' and 'No payment required.' add little for tool invocation, and the 'Current catalog:' paragraph is lengthy informational context rather than concise operational guidance.

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?

The description covers default scope, view selection, read_wip restrictions, and geographical availability. But with no output schema, it does not describe the return shape or pagination behavior, and it leaves sibling differentiation (notably vs. get_catalog) unaddressed, so the agent must infer some aspects from tool name and schema.

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 description coverage is 100%, so the schema already documents all five parameters. The description goes a step further by advising view='capabilities' first and by explaining that read_wip=true is for local loopback MCP internal review only, which adds selection context over the raw enum and boolean definitions.

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 identifies the resource and operation: 'Reads the published DaedalMap geometry catalog projection by default.' This distinguishes it from generic read operations, but it does not explicitly distinguish it from the sibling tool 'get_catalog', and the opening 'Free geography discovery' is vague marketing rather than useful purpose statement.

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 gives actionable internal guidance: '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 clarifies the default behavior and the local-loopback-only read_wip path. However, it does not explicitly contrast this tool with alternatives like get_catalog or state when not to use it.

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

All DaedalMap Geography Tools (loc_id) 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

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: point resolution, reference conversion, hierarchy traversal, geometry retrieval, export creation, job estimation, catalog discovery, and relationship comparison are all separated. The descriptions explicitly state what each tool does and what it does not do, preventing misselection. Even closely related tools like get_geometry, get_geometry_export, and estimate_geometry_package are differentiated by their roles (single-shape retrieval vs. export artifact vs. dry-run estimate).

Naming Consistency5/5

All 20 tool names follow a consistent verb_noun snake_case pattern (e.g., get_geometry, create_conversion_job, resolve_point, list_reference_systems). The verbs are action-oriented (get, create, estimate, resolve, compare, list, read) and each noun clearly indicates the subject. While a few like 'loc_id_info' and 'how_geometry_works' deviate slightly from the strict verb_noun structure, they still fit the overall style and are easy to predict.

Tool Count4/5

The 20 tools are slightly above the typical 3-15 range but still well-scoped for a comprehensive geocoding and geography service. The extra tools reflect the breadth of operations offered (discovery, conversion, estimation, export, resolution, relationship analysis), each earning its place. The count feels reasonable given the domain, though it approaches the upper boundary of what an agent might easily navigate.

Completeness5/5

The tool surface covers the full lifecycle of geocoding workflows: discovery (get_catalog, get_pack, read_geometry_catalog), point resolution (resolve_point), reference resolution (resolve_reference), identifier identification (identify_reference_system), hierarchy traversal (resolve_loc_id_scope, loc_id_info), geometry retrieval (get_geometry), relationship analysis (compare_geographies), conversion (convert_reference, create_conversion_job), export (create_geometry_export), and estimation (estimate_geometry_package, estimate_conversion_job). The inclusion of help tools (get_tool_help, how_geometry_works) and job status retrieval ensures no dead ends. The absence of destructive or update operations is consistent with a read-only geospatial data service, so the surface is appropriate.

Resources