Skip to main content
Glama

DaedalMap Geography Tools (loc_id)

by com.daedalmap

Resolve Point to loc_id

resolve_point
Read-only

Compact reverse geocoding. Converts one WGS84 point, or a bounded point list, into the latest-available administrative loc_id chain. Each chain row is intentionally small: loc_id, name, admin level, and vintage when available. This tool does not return polygons, hierarchy analysis, references, overlap percentages, lifecycle, provenance, or release-conversion detail. Pass the returned stack loc_ids to loc_id_info for details; use get_geometry for shapes and compare_geographies for relationships. Small exploratory calls may omit scope and resolve through the deepest served tier. Batches above the 25-point preview must declare exactly one country_scope and one target_admin_level; split multi-country input into one call per country. Cross-country admin-0/admin-1 batches may instead use bulk_preset. Anonymous callers pay above 25, while verified accounts receive included bulk throughput through 10,000 points. 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
latNoLatitude in WGS84 decimal degrees.
lonNoLongitude in WGS84 decimal degrees.
pointsNoPoints to resolve. Up to 25 may be exploratory. Above 25, country_scope and target_admin_level are required. Anonymous callers receive a payment challenge; verified accounts have included throughput through 10,000 points.
batch_idNoOptional caller-supplied batch id echoed in the result.
request_idNoOptional caller-supplied request id for tracing.
bulk_presetNoCross-country fast path that fixes the result level to admin_0 or admin_1. Use instead of country_scope; target_admin_level may be omitted.
country_hintNoAlias for country_scope for clients that already use hint terminology.
country_scopeNoISO3/admin_0 loc_id scope such as USA or CAN. Optional for up to 100 exploratory points and required for larger batches; every point must belong to this one country.
target_admin_levelNoStopping level such as admin_0 through admin_5. Optional for up to 100 exploratory points and required for larger batches.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / country_scope / description
      Previous value: -"ISO3/admin_0 loc_id scope such as USA or CAN. Optional for up to 25 exploratory points and required for larger batches; every point must belong to this one country."New value: +"ISO3/admin_0 loc_id scope such as USA or CAN. Optional for up to 100 exploratory points and required for larger batches; every point must belong to this one country."
    • changedInput schema / properties / target_admin_level / description
      Previous value: -"Stopping level such as admin_0 through admin_5. Optional for up to 25 exploratory points and required for larger batches."New value: +"Stopping level such as admin_0 through admin_5. Optional for up to 100 exploratory points and required for larger batches."
  2. Changed4 schema fields changed
    • addedInput schema / properties / bulk_preset
      Added value: +{
+  "description": "Cross-country fast path that fixes the result level to admin_0 or admin_1. Use instead of country_scope; target_admin_level may be omitted.",
+  "enum": [
+    "global_admin_0",
+    "global_admin_1"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / country_scope / description
      Previous value: -"Optional ISO3/admin_0 loc_id scope such as USA or CAN. Use only when every point in the request should be resolved inside that one country; this lets the runtime skip global country detection and use one country geometry bank."New value: +"ISO3/admin_0 loc_id scope such as USA or CAN. Optional for up to 25 exploratory points and required for larger batches; every point must belong to this one country."
    • changedInput schema / properties / points / description
      Previous value: -"Points to resolve. Hosted default free preview is 25 points; larger valid batches return a payment-required quote instead of executing for free."New value: +"Points to resolve. Up to 25 may be exploratory. Above 25, country_scope and target_admin_level are required. Anonymous callers receive a payment challenge; verified accounts have included throughput through 10,000 points."
    • changedInput schema / properties / target_admin_level / description
      Previous value: -"Optional stopping level such as admin_0 through admin_5. Omit for the normal complete chain through the deepest currently served tier."New value: +"Stopping level such as admin_0 through admin_5. Optional for up to 25 exploratory points and required for larger batches."
  3. Changed2 schema fields changed
    • removedInput schema / properties / include_geometry
      Removed value: -{
-  "description": "When true, include geometry in resolver internals where available. Default false to keep responses small.",
-  "type": "boolean"
-}
    • changedInput schema / properties / target_admin_level / description
      Previous value: -"Requested administrative level such as admin_0, admin_1, admin_2, admin_3, admin_4, or admin_5. Default admin_2. Use deepest/all only when the caller explicitly needs the deepest supported local geometry."New value: +"Optional stopping level such as admin_0 through admin_5. Omit for the normal complete chain through the deepest currently served tier."
  4. Changed5 schema fields changed
    • removedInput schema / properties / country
      Removed value: -{
-  "description": "Alias for parent_loc_id/country_scope when the scope is an ISO3 country code.",
-  "type": "string"
-}
    • changedInput schema / properties / country_hint / description
      Previous value: -"Alias for parent_loc_id/iso3. Use one country per paid/trusted bulk batch."New value: +"Alias for country_scope for clients that already use hint terminology."
    • changedInput schema / properties / country_scope / description
      Previous value: -"Alias for parent_loc_id when the scope is an admin_0/country loc_id."New value: +"Optional ISO3/admin_0 loc_id scope such as USA or CAN. Use only when every point in the request should be resolved inside that one country; this lets the runtime skip global country detection and use one country geometry bank."
    • removedInput schema / properties / iso3
      Removed value: -{
-  "description": "Alias for parent_loc_id/country_scope when the scope is an ISO3 country code.",
-  "type": "string"
-}
    • removedInput schema / properties / parent_loc_id
      Removed value: -{
-  "description": "Optional country scope such as USA, CAN, or IND. Required for paid/trusted bulk point batches over the free preview limit. Bulk should use one country and one target_admin_level per call.",
-  "type": "string"
-}
  5. Changed5 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Alias for parent_loc_id/country_scope when the scope is an ISO3 country code.",
+  "type": "string"
+}
    • addedInput schema / properties / country_hint
      Added value: +{
+  "description": "Alias for parent_loc_id/iso3. Use one country per paid/trusted bulk batch.",
+  "type": "string"
+}
    • addedInput schema / properties / country_scope
      Added value: +{
+  "description": "Alias for parent_loc_id when the scope is an admin_0/country loc_id.",
+  "type": "string"
+}
    • addedInput schema / properties / iso3
      Added value: +{
+  "description": "Alias for parent_loc_id/country_scope when the scope is an ISO3 country code.",
+  "type": "string"
+}
    • addedInput schema / properties / parent_loc_id
      Added value: +{
+  "description": "Optional country scope such as USA, CAN, or IND. Required for paid/trusted bulk point batches over the free preview limit. Bulk should use one country and one target_admin_level per call.",
+  "type": "string"
+}
  6. Changed2 schema fields changed
    • changedInput schema / properties / points / description
      Previous value: -"Points to resolve. Hosted default maximum is 25 points per call."New value: +"Points to resolve. Hosted default free preview is 25 points; larger valid batches return a payment-required quote instead of executing for free."
    • addedInput schema / properties / target_admin_level
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    }
+  ],
+  "description": "Requested administrative level such as admin_0, admin_1, admin_2, admin_3, admin_4, or admin_5. Default admin_2. Use deepest/all only when the caller explicitly needs the deepest supported local geometry."
+}
  7. Changed5 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "lat",
+      "lon"
+    ]
+  },
+  {
+    "required": [
+      "points"
+    ]
+  }
+]
    • addedInput schema / properties / batch_id
      Added value: +{
+  "description": "Optional caller-supplied batch id echoed in the result.",
+  "type": "string"
+}
    • addedInput schema / properties / include_geometry
      Added value: +{
+  "description": "When true, include geometry in resolver internals where available. Default false to keep responses small.",
+  "type": "boolean"
+}
    • addedInput schema / properties / points
      Added value: +{
+  "description": "Points to resolve. Hosted default maximum is 25 points per call.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "string"
+          }
+        ],
+        "description": "Optional caller point identifier echoed in the result."
+      },
+      "lat": {
+        "description": "Latitude in WGS84 decimal degrees.",
+        "maximum": 90,
+        "minimum": -90,
+        "type": "number"
+      },
+      "lon": {
+        "description": "Longitude in WGS84 decimal degrees.",
+        "maximum": 180,
+        "minimum": -180,
+        "type": "number"
+      },
+      "row_index": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "string"
+          }
+        ],
+        "description": "Optional caller row identifier echoed in the result."
+      }
+    },
+    "required": [
+      "lat",
+      "lon"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "lat",
-  "lon"
-]
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With readOnlyHint=true already covering the safety profile, the description adds substantial behavioral context: output rows are intentionally small, the tool does not return polygons or hierarchy analysis, and results reflect the latest available administrative chain. It also discloses throughput and payment behavior for anonymous vs verified callers, and explains how country catalog depth affects results.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and exclusions, then moves through usage constraints, billing, and catalog depth in a logical order. It is longer than strictly necessary, especially the current-catalog country list, but every major section adds decision-relevant context for a 9-parameter tool with no output schema.

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?

Despite having no output schema, the description tells the agent exactly what each chain row contains: loc_id, name, admin level, and vintage. It covers exclusions, sibling routing, parameter requirements, billing thresholds, and geographic coverage, leaving no critical gap for an agent deciding whether and how to call this tool.

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 individual parameter definitions are already handled. The description adds value by clarifying conditional parameter behavior: 'exactly one' country_scope and target_admin_level above 25 points, the need to split multi-country input, and bulk_preset as a substitute for cross-country batches. Some billing and threshold details duplicate schema text, but the added constraints are useful.

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?

The description opens with a precise verb and resource: 'Converts one WGS84 point, or a bounded point list, into the latest-available administrative loc_id chain.' It also differentiates itself by explicitly listing what it does not return and names the sibling tools that should be used instead, so an agent can distinguish this from get_geometry, compare_geographies, and loc_id_info.

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

Usage Guidelines5/5

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

Usage rules are explicit: small exploratory calls may omit scope, batches above 25 must declare exactly one country_scope and target_admin_level, multi-country input must be split, and bulk_preset is the recommended path for cross-country admin-0/admin-1 batches. The description also tells the agent when to route to loc_id_info, get_geometry, and compare_geographies, which is strong alternative guidance.

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