Skip to main content
Glama

DaedalMap Disaster and Geospatial Data

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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Despite readOnlyHint=true already covering safety, the description adds meaningful behavior: row contents, exclusions, small-vs-bulk limits, anonymous vs verified throughput, and automatic depth by catalog coverage. I deduct a point because the stated 25-point cutoff conflicts with the schema's 100-point exploratory allowance, weakening trust in the behavioral contract.

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?

Front-loaded with the core action and output, then organized into exclusions, sibling routing, batching rules, and catalog context. Long, but each block earns its place and the catalog paragraph gives necessary context for expected admin depth.

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?

This is a complex 9-parameter tool with no output schema, and the description explains return-row fields as loc_id, name, admin level, and vintage. However, it omits the exact response structure/ordering and contains the 25-vs-100 inconsistency, so an agent does not yet have everything needed to invoke it with certainty.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description does add practical context around country_scope/target_admin_level and bulk_preset, but its threshold rule conflicts with the schema ('above 25' vs 'up to 100 exploratory points'), so it does not reliably clarify parameter behavior beyond the schema.

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?

Opens with 'Compact reverse geocoding' and states it converts one WGS84 point or a bounded point list into a latest-available administrative loc_id chain. It differentiates itself by explicitly listing what it does not return (polygons, hierarchy analysis, references, etc.) and pointing to sibling tools that cover those needs.

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?

Gives explicit routing: pass stack loc_ids to loc_id_info, use get_geometry for shapes, compare_geographies for relationships, and bulk_preset for cross-country admin-0/admin-1 batches. It also states the batching rule and the need to split multi-country input per country.

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