Skip to main content
Glama

DaedalMap Disaster and Geospatial Data

Resolve Point(s) (Shallow)

resolve_point
Read-only

Compact first-pass reverse geocoding for one WGS84 coordinate or a bounded point array. Returns administrative loc_id chains through Admin 3 without opening deep partitions or side-family shape banks. Use a returned shallow loc_id with resolve_deep_point for Admin 4-6 or one explicit family. Single and bulk requests share this contract; access limits are based on point count. 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.
pointsNoBounded WGS84 point array. Use top-level lat/lon instead for one point.
batch_idNoOptional caller-supplied batch id echoed for point arrays.
request_idNoOptional caller-supplied request id for tracing.
target_admin_levelNoOptional exact requested level from Admin 0-3. Omit it to return the deepest available shallow level.
include_marine_contextNoInclude parallel Marine overlaps for land matches. Defaults to true; set false for fast administrative loc_id previews. Offshore Marine fallback still applies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "points"
      +      ]
      +    },
      +    "required": [
      +      "lat",
      +      "lon"
      +    ]
      +  },
      +  {
      +    "not": {
      +      "anyOf": [
      +        {
      +          "required": [
      +            "lat"
      +          ]
      +        },
      +        {
      +          "required": [
      +            "lon"
      +          ]
      +        }
      +      ]
      +    },
      +    "required": [
      +      "points"
      +    ]
      +  }
      +]
    • addedInput schema / properties / batch_id
      Added value: +{
      +  "description": "Optional caller-supplied batch id echoed for point arrays.",
      +  "type": "string"
      +}
    • addedInput schema / properties / points
      Added value: +{
      +  "description": "Bounded WGS84 point array. Use top-level lat/lon instead for one point.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "string"
      +          }
      +        ]
      +      },
      +      "lat": {
      +        "maximum": 90,
      +        "minimum": -90,
      +        "type": "number"
      +      },
      +      "lon": {
      +        "maximum": 180,
      +        "minimum": -180,
      +        "type": "number"
      +      },
      +      "row_index": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "string"
      +          }
      +        ]
      +      }
      +    },
      +    "required": [
      +      "lat",
      +      "lon"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "lat",
      -  "lon"
      -]
  2. Changed10 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
      -  {
      -    "required": [
      -      "lat",
      -      "lon"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "points"
      -    ]
      -  }
      -]
    • removedInput schema / properties / admin_1_scope
      Removed value: -{
      -  "description": "Required in deep mode. One Admin 1 loc_id returned by the standard pass, such as USA-CA. Every point must belong to this owner partition.",
      -  "type": "string"
      -}
    • removedInput schema / properties / batch_id
      Removed value: -{
      -  "description": "Optional caller-supplied batch id echoed in the result.",
      -  "type": "string"
      -}
    • removedInput schema / properties / bulk_preset
      Removed value: -{
      -  "description": "Cross-country standard-mode path that fixes the exact result level. Use instead of country_scope; target_admin_level may be omitted.",
      -  "enum": [
      -    "global_admin_0",
      -    "global_admin_1"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / country_hint
      Removed value: -{
      -  "description": "Alias for country_scope for clients that already use hint terminology.",
      -  "type": "string"
      -}
    • removedInput schema / properties / country_scope
      Removed value: -{
      -  "description": "ISO3/Admin 0 loc_id scope such as USA or CAN. Optional in standard mode and required in deep mode; every deep-mode point must belong to this one country.",
      -  "type": "string"
      -}
    • removedInput schema / properties / lookup_mode
      Removed value: -{
      -  "description": "Standard (default) caps I/O at Admin 3. Deep requires exactly one country_scope and one admin_1_scope, and opens at most one deep partition.",
      -  "enum": [
      -    "standard",
      -    "deep"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / points
      Removed value: -{
      -  "description": "Points to resolve. Standard mode accepts cross-country batches and caps geometry I/O at Admin 3. Deep batches require one country_scope and one admin_1_scope; larger deep batches also require target_admin_level. Anonymous callers may receive a payment challenge; verified accounts have included throughput through 10,000 points.",
      -  "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"
      -}
    • changedInput schema / properties / target_admin_level / description
      Previous value: -"Optional exact requested level. Standard mode accepts Admin 0-3; deep mode accepts Admin 4-6. Omit it to return the deepest available level permitted by the selected mode."New value: +"Optional exact requested level from Admin 0-3. Omit it to return the deepest available shallow level."
    • addedInput schema / required
      Added value: +[
      +  "lat",
      +  "lon"
      +]
  3. Changed7 schema fields changed
    • addedInput schema / properties / admin_1_scope
      Added value: +{
      +  "description": "Required in deep mode. One Admin 1 loc_id returned by the standard pass, such as USA-CA. Every point must belong to this owner partition.",
      +  "type": "string"
      +}
    • changedInput schema / properties / bulk_preset / description
      Previous value: -"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."New value: +"Cross-country standard-mode path that fixes the exact result level. Use instead of country_scope; target_admin_level may be omitted."
    • changedInput schema / properties / country_scope / description
      Previous 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."New value: +"ISO3/Admin 0 loc_id scope such as USA or CAN. Optional in standard mode and required in deep mode; every deep-mode point must belong to this one country."
    • addedInput schema / properties / include_marine_context
      Added value: +{
      +  "description": "Include parallel Marine overlaps for land matches. Defaults to true; set false for fast administrative loc_id previews. Offshore Marine fallback still applies.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / lookup_mode
      Added value: +{
      +  "description": "Standard (default) caps I/O at Admin 3. Deep requires exactly one country_scope and one admin_1_scope, and opens at most one deep partition.",
      +  "enum": [
      +    "standard",
      +    "deep"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / points / description
      Previous 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."New value: +"Points to resolve. Standard mode accepts cross-country batches and caps geometry I/O at Admin 3. Deep batches require one country_scope and one admin_1_scope; larger deep batches also require target_admin_level. Anonymous callers may receive a payment challenge; verified accounts have included throughput through 10,000 points."
    • changedInput schema / properties / target_admin_level / description
      Previous value: -"Stopping level such as admin_0 through admin_5. Optional for up to 100 exploratory points and required for larger batches."New value: +"Optional exact requested level. Standard mode accepts Admin 0-3; deep mode accepts Admin 4-6. Omit it to return the deepest available level permitted by the selected mode."
  4. 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."
  5. 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."
  6. 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."
  7. 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"
      -}
  8. 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"
      +}
  9. 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."
      +}
  10. 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"
      -]
  11. Added

TDQS

A4.6/5.0
Behavior5/5

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

The readOnlyHint annotation already signals a safe read operation, and the description adds valuable behavior beyond that: it does not open deep partitions or side-family shape banks, access limits depend on point count, and country releases automatically extend results. This gives the agent a clear behavioral model without contradicting the annotation.

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 first three sentences are tight and front-loaded, immediately establishing purpose, depth, and the handoff to resolve_deep_point. The final catalog paragraph is somewhat longer than strictly necessary, but it earns its place by clarifying expected depth and geographic coverage.

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?

For a read-only reverse-geocoding tool with no output schema, the description explains what is returned, the maximum admin depth, the deeper-tool handoff, bulk behavior, access-limit basis, and current geographic coverage. An agent has enough context to select and invoke this tool correctly without consulting additional sources.

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?

The input schema already describes all seven parameters, including the lat/lon vs. points oneOf constraint, so the schema carries most of the parameter burden. The description adds only general context like 'bounded point array' and access limits based on point count, which is useful but does not deepen the meaning of specific parameters such as target_admin_level or include_marine_context.

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 names a specific operation ('first-pass reverse geocoding'), the resource ('one WGS84 coordinate or a bounded point array'), and the depth scope ('through Admin 3'). It explicitly contrasts itself with resolve_deep_point, so an agent can distinguish the sibling tools immediately.

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?

It explicitly says to use resolve_deep_point for Admin 4-6 or an explicit family, and it clarifies that single and bulk requests share the same contract. The catalog paragraph also explains when deeper tiers are automatically returned, removing ambiguity about worldwide vs. expanded country coverage.

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.