Skip to main content
Glama

DaedalMap Reverse Geocoding (coordinates to loc_id)

by com.daedalmap
OverviewDiscussionsAdmin

Server Details

Convert WGS84 coordinates to the latest available administrative loc_id chain.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
95.4% over 43 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
xyver/daedal-map
GitHub Stars
2
Server Listing
daedal-map

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation4/5

The two resolution tools (resolve_point and resolve_deep_point) are clearly differentiated as first-pass versus second-pass, with explicit input/output contracts. The discovery tools (get_catalog, get_pack, get_tool_help) have distinct roles but share similar progressive/raw-URL phrasing, which could cause momentary confusion about which to call first.

Naming Consistency5/5

All tool names use snake_case with a consistent verb_noun pattern: get_catalog, get_pack, get_tool_help, resolve_point, resolve_deep_point. The only minor variation is the inserted 'deep' modifier in resolve_deep_point, but it remains predictable and readable.

Tool Count5/5

Five tools is well-scoped for a reverse geocoding service with a two-step resolution workflow plus discovery and help utilities. Each tool has a clear role without redundancy, and the count sits comfortably in the typical 3-15 range.

Completeness4/5

The surface covers the core reverse geocoding lifecycle: shallow and deep resolution, plus catalog/pack discovery and tool help. A minor gap is the lack of a direct tool to retrieve metadata or hierarchy for a resolved loc_id, but this may be outside the stated scope.

Available Tools

5 tools
get_catalogList Available Packs and Geometry FamiliesA
Read-onlyIdempotent
Inspect

Discover data packs or geometry families progressively: lite selection, full metric/query inventory, or a raw catalog download URL. Choose one result and call get_pack next. 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
detailNoUse lite to select a pack, full for expanded metric/query inventories, or download for the complete raw catalog URL.lite
loc_idNoOptional DaedalMap loc_id for catalog='data'. Combine with time_range to discover packs confirmed for both place and time. For place details without pack filtering, use get_loc_id_info.
catalogNoCatalog family. The geography facade defaults to geometry; other facades default to data.data
time_rangeNoOptional inclusive discovery window for catalog='data'. At least one bound is required.
country_scopeNoOptional ISO3 focus for catalog='geometry' with detail='lite'.

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNo
packsNo
detailNo
reasonNo
catalogNo
guidanceNo
warningsNo
next_stepNo
pack_countNo
provenanceNo
request_idNo
download_urlNo
generated_atNo
clarificationNo
tool_familiesNo
catalog_versionNo

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't repeat those. It adds valuable behavioral context: the tool automatically returns deeper administrative tiers for certain countries, and the progressive discovery behavior. This goes beyond annotations and helps the agent understand the tool's adaptive output.

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 sentence is efficient and front-loaded, stating the core function and the three discovery levels. The second sentence gives workflow guidance. The second paragraph adds catalog scope context, which is useful but slightly verbose. Overall, it's well-structured and each sentence earns its place.

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's complexity (5 optional parameters, nested object, enums) and the presence of an output schema, the description is complete. It explains the catalog's geographic scope and the progressive workflow, which the schema does not. It doesn't need to cover return values because the output schema exists. The description provides sufficient context for correct invocation.

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 description coverage is 100%, so each parameter already has clear documentation. The main description doesn't add parameter-specific semantics beyond the workflow context (e.g., progressive detail levels), which the schema already explains. This meets the baseline of 3 for high coverage.

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 clearly states the tool's purpose: to discover data packs or geometry families with progressive levels (lite, full, download). It distinguishes itself from get_pack by explicitly routing the agent to call get_pack next, and from get_data by focusing on catalog listing rather than data retrieval. The verb 'discover' and resource 'catalog' are specific.

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 a clear workflow: start with lite to select a pack, then call get_pack. It also mentions that get_loc_id_info is the alternative for place details without pack filtering (in the parameter description). However, it doesn't explicitly state when not to use this tool versus get_data or get_tool_help, though the workflow implication is strong.

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

get_packInspect One Selected Pack or Geometry FamilyA
Read-onlyIdempotent
Inspect

Inspect one selected data pack or geometry family progressively: lite starter contract, full MCP query metadata, or a raw metadata download URL. Use its next_step to retrieve data or call the preferred geometry tool.

ParametersJSON Schema
NameRequiredDescriptionDefault
detailNoUse lite to decide and start, full for detailed MCP query metadata, or download for the complete raw metadata file.lite
catalogNoMetadata family. When omitted, geometry facades default to geometry and known geometry-family ids are inferred; all other calls default to data.
pack_idYesPack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
release_unitNoOptional non-country geometry release unit such as GLOBAL or MARINE. Do not combine with country_scope.
country_scopeNoOptional ISO3 country for a geometry family. Omit it to learn which countries publish the family; provide it for country-specific versions, vintages, levels, and artifacts.

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNo
detailNo
reasonNo
catalogNo
pack_idNo
sourcesNo
guidanceNo
warningsNo
full_callNo
next_stepNo
provenanceNo
request_idNo
download_urlNo
clarificationNo
download_callNo
material_policyNo

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavioral value by revealing that results include a next_step for progression and that detail levels map to lite vs full metadata vs download URL. This goes beyond what annotations alone provide.

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

Conciseness5/5

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

Two tight sentences front-load the core purpose and then give the key follow-up behavior. There is no filler or redundant restatement of the schema.

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?

With a rich input schema and an output schema, the description covers the essential workflow and progression. The only mild gap is that 'preferred geometry tool' is not named explicitly, but the sibling list and schema make the intended routing reasonably discoverable.

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 schema already documents all parameters in detail. The description adds only mild semantic framing ('lite starter contract') and mostly restates the detail-level behavior already present in the schemas.

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 uses a specific verb, 'Inspect', and a specific resource, 'one selected data pack or geometry family', and names three progressive modes (lite, full, download). It also differentiates from siblings by framing get_pack as operating on a single selected item while get_catalog lists and get_data retrieves data.

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 guidance: use it to inspect a selected pack, and then 'Use its next_step to retrieve data or call the preferred geometry tool.' It implies a sequential workflow but does not explicitly state when to prefer get_data or get_catalog instead, so it falls just short of full exclusion guidance.

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

get_tool_helpGet Tool HelpA
Read-onlyIdempotent
Inspect

Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.

ParametersJSON Schema
NameRequiredDescriptionDefault
topicNoWorkflow overview. Do not combine with tool_name.
questionNoOptional question used only with a topic overview.
tool_nameNoExact tool name from tools/list. Do not combine with topic.

Output Schema

ParametersJSON Schema
NameRequiredDescription
okNo
errorNo
titleNo
accessNo
reasonNo
purposeNo
examplesNo
guidanceNo
warningsNo
next_stepNo
tool_nameNo
provenanceNo
request_idNo
input_schemaNo
clarificationNo
recommended_next_callsNo
important_output_fieldsNo

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds a bit of behavioral context by mentioning 'exact contract' and 'bounded workflow overview', but it does not disclose potential error conditions or response formats. This is acceptable given the annotations, so a 3 is appropriate.

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

Conciseness5/5

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

The description is a single, well-structured sentence that efficiently presents both modes without redundancy. Every phrase adds value, and it is front-loaded with the primary action.

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 is adequate but relies heavily on the schema for constraints (e.g., oneOf logic, enum values, mutual exclusivity). It does not mention optional parameters or edge cases, but given the rich schema and annotations, it covers the essential purpose. A 3 reflects that it is sufficient but not exhaustive.

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 description coverage is 100% and each parameter already has a thorough description (e.g., 'Do not combine with tool_name'). The tool description adds no extra parameter detail beyond the schema, so the baseline of 3 applies.

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 clearly states the tool's purpose: describe a tool (with its exact contract) or return a workflow overview for a supported topic. It uses specific verbs and resources, and the two modes are distinct. This differentiates it from sibling data-fetching tools like get_data and get_catalog.

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 implies when to use each mode by stating the two options, and the schema enforces mutual exclusivity. However, it does not explicitly name alternatives or state when NOT to use this tool (e.g., for actual data retrieval). Still, the purpose is clear enough for an agent to infer correct usage.

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

resolve_deep_pointResolve Point(s) (Deep)A
Read-onlyIdempotent
Inspect

Second-pass resolution for one WGS84 coordinate or a bounded point array. Supply one shared shallow_loc_id returned by resolve_point and one canonical family from get_catalog(catalog='geometry'). family defaults to administrative; shape-backed families use direct bbox-to-exact-shape lookup without crosswalks. Single and bulk requests share this scoped contract. 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
latNoLatitude in WGS84 decimal degrees.
lonNoLongitude in WGS84 decimal degrees.
familyNoOne family selector. Defaults to administrative; use marine for the direct Marine resolver, or a canonical country family such as postal_area, watershed, or land_management_region.administrative
pointsNoPoints already known to fall within the supplied shallow_loc_id scope.
batch_idNoOptional caller-supplied batch id echoed for point arrays.
request_idNoOptional caller-supplied request id for tracing.
shallow_loc_idYesThe deepest canonical Admin 1-3 loc_id returned by resolve_point, such as USA-NY-061-009903.
target_admin_levelNoOptional exact Admin 4-6 level. Omit for the deepest available match.

Output Schema

ParametersJSON Schema
NameRequiredDescription
okNo
errorNo
pointNo
stackNo
familyNo
reasonNo
matchedNo
resultsNo
batch_idNo
guidanceNo
warningsNo
join_keysNo
next_stepNo
request_idNo
point_countNo
clarificationNo
family_resultNo
meter_receiptNo
resolved_countNo
shallow_loc_idNo
deeper_availableNo
overlap_familiesNo
unresolved_countNo
settlement_receiptNo
deepest_resolved_familyNo
deepest_resolved_loc_idNo
deepest_resolved_admin_levelNo
available_deeper_admin_levelsNo

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond that: it reveals the bbox-to-exact-shape lookup strategy for shape-backed families and the scoped contract shared by single and bulk requests, plus geographic coverage nuances such as automatic deeper tiers for certain countries. 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.

Conciseness4/5

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

The core usage description is front-loaded and tight: purpose, required inputs, family default, and lookup behavior fit into the first few sentences. The final 'Current catalog' paragraph is informative but somewhat lengthy and could be trimmed; still, it is organized and not redundant with the schema.

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?

For a moderately complex tool with 8 parameters, a oneOf constraint, and an output schema, the description covers the essential operational context: second-pass nature, required upstream inputs, family behavior, and data availability. The points array scope is reinforced ('bounded point array' matches the schema's 'Points already known to fall within the supplied shallow_loc_id scope'), and the output schema covers return values.

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 baseline is 3. The description adds value by explaining how to source the shallow_loc_id and family parameters, that family defaults to administrative, and that shape-backed families behave differently. This goes beyond the schema's field-level descriptions, though it doesn't detail every parameter because the schema already does.

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 'Second-pass resolution for one WGS84 coordinate or a bounded point array,' naming a specific verb, resource, and scope. It also explicitly ties to sibling tools by requiring a shallow_loc_id 'returned by resolve_point' and a family 'from get_catalog(catalog='geometry')', making the tool's role and differentiation unmistakable.

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 clearly states the invocation contract: supply a shallow_loc_id from resolve_point and a canonical family from get_catalog. It also notes that family defaults to administrative and that shape-backed families use direct lookup without crosswalks, giving clear context on when to use this deep-resolution path. It doesn't explicitly enumerate when-not-to-use cases, so it falls just short of full exclusionary guidance.

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

resolve_pointResolve Point(s) (Shallow)A
Read-onlyIdempotent
Inspect

Compact first-pass reverse geocoding for one WGS84 coordinate or a bounded point array. Returns the deepest available administrative loc_id chain: the global baseline reaches Admin 2, while adopted country query banks may reach Admin 3. It does not open 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.

ParametersJSON 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_contextNoOpt in to parallel Marine overlaps for land matches. Defaults to false so ordinary administrative resolution stays lightweight. Offshore Marine fallback still applies.

Output Schema

ParametersJSON Schema
NameRequiredDescription
okNo
errorNo
pointNo
stackNo
familyNo
reasonNo
matchedNo
resultsNo
batch_idNo
guidanceNo
warningsNo
join_keysNo
next_stepNo
request_idNo
point_countNo
clarificationNo
family_resultNo
meter_receiptNo
resolved_countNo
shallow_loc_idNo
deeper_availableNo
overlap_familiesNo
unresolved_countNo
settlement_receiptNo
deepest_resolved_familyNo
deepest_resolved_loc_idNo
deepest_resolved_admin_levelNo
available_deeper_admin_levelsNo

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavioral context: the returned loc_id chain depth (baseline Admin 2, adopted banks to Admin 3), what it explicitly does NOT do (no deep partitions, no side-family shape banks), and that access limits scale with point count. This is substantive disclosure beyond the annotations.

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 two sentences are tightly front-loaded and carry the core scope plus the deep/shallow routing. The trailing catalog paragraph is informative about coverage depth but is comparatively verbose and partly overlaps what get_catalog would provide.

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?

With an output schema present, return values needn't be spelled out, and annotations cover the safety profile. The description still supplies scope, alternative routing, depth guarantees, and access-limit behavior, leaving nothing an agent needs to call it correctly.

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 description coverage is 100%, so the schema already documents lat/lon bounds, the points array, target_admin_level's Admin 0-3 range, and the marine flag. The description mostly restates these (e.g. deepest available shallow level) rather than adding syntax or edge-case semantics, so the baseline 3 applies.

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?

States a specific verb (reverse geocode/resolve) and resource (one WGS84 coordinate or bounded point array), and immediately positions itself against the sibling resolve_deep_point by scope (shallow vs deep). An agent can distinguish it from resolve_deep_point without opening either schema.

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?

Explicitly routes the agent: use this for a compact first pass, then feed the returned shallow loc_id into resolve_deep_point for Admin 4-6 or one explicit family. The alternative and the condition that selects it are both named, and it states that single and bulk requests share the same contract.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedresolve_point2 fields changed
      • addedInput schema / properties / include_marine_context / default
        Added value: +false
      • changedInput schema / properties / include_marine_context / description
        Previous value: -"Include parallel Marine overlaps for land matches. Defaults to true; set false for fast administrative loc_id previews. Offshore Marine fallback still applies."New value: +"Opt in to parallel Marine overlaps for land matches. Defaults to false so ordinary administrative resolution stays lightweight. Offshore Marine fallback still applies."
  2. 2 tool updates
    • Changedresolve_deep_point1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "point",
+        "stack"
+      ]
+    },
+    {
+      "required": [
+        "point",
+        "family",
+        "family_result"
+      ]
+    },
+    {
+      "required": [
+        "point_count",
+        "results"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "available_deeper_admin_levels": {
+      "type": "array"
+    },
+    "batch_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "deeper_available": {
+      "type": "boolean"
+    },
+    "deepest_resolved_admin_level": {
+      "type": [
+        "string",
+        "integer",
+        "null"
+      ]
+    },
+    "deepest_resolved_family": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "deepest_resolved_loc_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "family": {
+      "type": "string"
+    },
+    "family_result": {
+      "type": "object"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "join_keys": {
+      "type": "object"
+    },
+    "matched": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "meter_receipt": {
+      "type": "object"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "anyOf": [
+        {
+          "required": [
+            "action"
+          ]
+        },
+        {
+          "required": [
+            "tool"
+          ]
+        }
+      ],
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "overlap_families": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "point": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "lat": {
+              "type": "number"
+            },
+            "lon": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "lat",
+            "lon"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "point_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resolved_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "error": {
+            "additionalProperties": true,
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "details": {
+                "type": "object"
+              },
+              "message": {
+                "type": "string"
+              },
+              "retry_hint": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "message"
+            ],
+            "type": "object"
+          },
+          "id": {
+            "type": [
+              "string",
+              "integer",
+              "null"
+            ]
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "row_index": {
+            "type": [
+              "string",
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "settlement_receipt": {
+      "type": "object"
+    },
+    "shallow_loc_id": {
+      "type": "string"
+    },
+    "stack": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unresolved_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
    • Changedresolve_point1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "point",
+        "stack"
+      ]
+    },
+    {
+      "required": [
+        "point",
+        "family",
+        "family_result"
+      ]
+    },
+    {
+      "required": [
+        "point_count",
+        "results"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "available_deeper_admin_levels": {
+      "type": "array"
+    },
+    "batch_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "deeper_available": {
+      "type": "boolean"
+    },
+    "deepest_resolved_admin_level": {
+      "type": [
+        "string",
+        "integer",
+        "null"
+      ]
+    },
+    "deepest_resolved_family": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "deepest_resolved_loc_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "family": {
+      "type": "string"
+    },
+    "family_result": {
+      "type": "object"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "join_keys": {
+      "type": "object"
+    },
+    "matched": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "meter_receipt": {
+      "type": "object"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "anyOf": [
+        {
+          "required": [
+            "action"
+          ]
+        },
+        {
+          "required": [
+            "tool"
+          ]
+        }
+      ],
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "overlap_families": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "point": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "lat": {
+              "type": "number"
+            },
+            "lon": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "lat",
+            "lon"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "point_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resolved_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "error": {
+            "additionalProperties": true,
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "details": {
+                "type": "object"
+              },
+              "message": {
+                "type": "string"
+              },
+              "retry_hint": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "message"
+            ],
+            "type": "object"
+          },
+          "id": {
+            "type": [
+              "string",
+              "integer",
+              "null"
+            ]
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "row_index": {
+            "type": [
+              "string",
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "settlement_receipt": {
+      "type": "object"
+    },
+    "shallow_loc_id": {
+      "type": "string"
+    },
+    "stack": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unresolved_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. 1 tool update
    • Changedget_catalog2 fields changed
      • addedInput schema / properties / loc_id
        Added value: +{
+  "description": "Optional DaedalMap loc_id for catalog='data'. Combine with time_range to discover packs confirmed for both place and time. For place details without pack filtering, use get_loc_id_info.",
+  "type": "string"
+}
      • addedInput schema / properties / time_range
        Added value: +{
+  "additionalProperties": false,
+  "description": "Optional inclusive discovery window for catalog='data'. At least one bound is required.",
+  "properties": {
+    "end": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        }
+      ]
+    },
+    "start": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}
  4. 7 tool updates
    • Changedget_catalog9 fields changed
      • addedInput schema / properties / catalog
        Added value: +{
+  "default": "data",
+  "description": "Catalog family. The geography facade defaults to geometry; other facades default to data.",
+  "enum": [
+    "data",
+    "geometry"
+  ],
+  "type": "string"
+}
      • addedInput schema / properties / country_scope
        Added value: +{
+  "description": "Optional ISO3 focus for catalog='geometry' with detail='lite'.",
+  "type": "string"
+}
      • addedInput schema / properties / detail
        Added value: +{
+  "default": "lite",
+  "description": "Use lite to select a pack, full for expanded metric/query inventories, or download for the complete raw catalog URL.",
+  "enum": [
+    "lite",
+    "full",
+    "download"
+  ],
+  "type": "string"
+}
      • changedOutput schema / anyOf
        Previous value: -[
-  {
-    "required": [
-      "packs"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "catalog",
+      "detail"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
      • addedOutput schema / properties / catalog
        Added value: +{
+  "enum": [
+    "data",
+    "geometry"
+  ],
+  "type": "string"
+}
      • addedOutput schema / properties / detail
        Added value: +{
+  "enum": [
+    "lite",
+    "full",
+    "download"
+  ],
+  "type": "string"
+}
      • addedOutput schema / properties / download_url
        Added value: +{
+  "type": "string"
+}
      • addedOutput schema / properties / next_step / anyOf
        Added value: +[
+  {
+    "required": [
+      "action"
+    ]
+  },
+  {
+    "required": [
+      "tool"
+    ]
+  }
+]
      • removedOutput schema / properties / next_step / required
        Removed value: -[
-  "action"
-]
    • Changedget_pack13 fields changed
      • addedInput schema / properties / catalog
        Added value: +{
+  "description": "Metadata family. When omitted, geometry facades default to geometry and known geometry-family ids are inferred; all other calls default to data.",
+  "enum": [
+    "data",
+    "geometry"
+  ],
+  "type": "string"
+}
      • addedInput schema / properties / country_scope
        Added value: +{
+  "description": "Optional ISO3 country for a geometry family. Omit it to learn which countries publish the family; provide it for country-specific versions, vintages, levels, and artifacts.",
+  "pattern": "^[A-Za-z]{3}$",
+  "type": "string"
+}
      • changedInput schema / properties / detail / description
        Previous value: -"Use lite for normal discovery. Use full only for one selected pack when its complete public metadata is required."New value: +"Use lite to decide and start, full for detailed MCP query metadata, or download for the complete raw metadata file."
      • changedInput schema / properties / detail / enum
        Previous value: -[
-  "lite",
-  "full"
-]New value: +[
+  "lite",
+  "full",
+  "download"
+]
      • addedInput schema / properties / release_unit
        Added value: +{
+  "description": "Optional non-country geometry release unit such as GLOBAL or MARINE. Do not combine with country_scope.",
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}
      • changedOutput schema / anyOf
        Previous value: -[
-  {
-    "required": [
-      "pack_id"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "catalog",
+      "pack_id",
+      "detail"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
      • addedOutput schema / properties / catalog
        Added value: +{
+  "enum": [
+    "data",
+    "geometry"
+  ],
+  "type": "string"
+}
      • addedOutput schema / properties / detail
        Added value: +{
+  "enum": [
+    "lite",
+    "full",
+    "download"
+  ],
+  "type": "string"
+}
      • addedOutput schema / properties / download_call
        Added value: +{
+  "type": "object"
+}
      • addedOutput schema / properties / download_url
        Added value: +{
+  "type": "string"
+}
      • addedOutput schema / properties / full_call
        Added value: +{
+  "type": "object"
+}
      • addedOutput schema / properties / next_step / anyOf
        Added value: +[
+  {
+    "required": [
+      "action"
+    ]
+  },
+  {
+    "required": [
+      "tool"
+    ]
+  }
+]
      • removedOutput schema / properties / next_step / required
        Removed value: -[
-  "action"
-]
    • Changedget_tool_help7 fields changed
      • addedInput schema / oneOf
        Added value: +[
+  {
+    "not": {
+      "required": [
+        "topic"
+      ]
+    },
+    "required": [
+      "tool_name"
+    ]
+  },
+  {
+    "not": {
+      "required": [
+        "tool_name"
+      ]
+    },
+    "required": [
+      "topic"
+    ]
+  }
+]
      • addedInput schema / properties / question
        Added value: +{
+  "description": "Optional question used only with a topic overview.",
+  "type": "string"
+}
      • changedInput schema / properties / tool_name / description
        Previous value: -"Exact tool name from tools/list."New value: +"Exact tool name from tools/list. Do not combine with topic."
      • addedInput schema / properties / topic
        Added value: +{
+  "description": "Workflow overview. Do not combine with tool_name.",
+  "enum": [
+    "overview",
+    "data",
+    "disasters",
+    "custom_data",
+    "geometry"
+  ],
+  "type": "string"
+}
      • removedInput schema / required
        Removed value: -[
-  "tool_name"
-]
      • addedOutput schema / properties / next_step / anyOf
        Added value: +[
+  {
+    "required": [
+      "action"
+    ]
+  },
+  {
+    "required": [
+      "tool"
+    ]
+  }
+]
      • removedOutput schema / properties / next_step / required
        Removed value: -[
-  "action"
-]
    • Changedresolve_deep_point4 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": "Points already known to fall within the supplied shallow_loc_id scope.",
+  "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"
+}
      • changedInput schema / required
        Previous value: -[
-  "lat",
-  "lon",
-  "shallow_loc_id"
-]New value: +[
+  "shallow_loc_id"
+]
    • Removedresolve_deep_points
    • Changedresolve_point4 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"
-]
    • Removedresolve_points
  5. 1 tool update
    • Changedget_pack1 field changed
      • addedInput schema / properties / detail
        Added value: +{
+  "default": "lite",
+  "description": "Use lite for normal discovery. Use full only for one selected pack when its complete public metadata is required.",
+  "enum": [
+    "lite",
+    "full"
+  ],
+  "type": "string"
+}
  6. 2 tool updates
    • Changedresolve_deep_point5 fields changed
      • removedInput schema / properties / admin_1_loc_id
        Removed value: -{
-  "description": "Exactly one Admin 1 loc_id from resolve_point, such as USA-CA.",
-  "minLength": 5,
-  "type": "string"
-}
      • addedInput schema / properties / family
        Added value: +{
+  "default": "administrative",
+  "description": "One family selector. Defaults to administrative; use marine for the direct Marine resolver, or a canonical country family such as postal_area, watershed, or land_management_region.",
+  "pattern": "^[a-z0-9_]+$",
+  "type": "string"
+}
      • removedInput schema / properties / include_marine_context
        Removed value: -{
-  "description": "Include parallel Marine overlaps. Defaults to true.",
-  "type": "boolean"
-}
      • addedInput schema / properties / shallow_loc_id
        Added value: +{
+  "description": "The deepest canonical Admin 1-3 loc_id returned by resolve_point, such as USA-NY-061-009903.",
+  "minLength": 5,
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "lat",
-  "lon",
-  "admin_1_loc_id"
-]New value: +[
+  "lat",
+  "lon",
+  "shallow_loc_id"
+]
    • Changedresolve_deep_points6 fields changed
      • removedInput schema / properties / admin_1_loc_id
        Removed value: -{
-  "description": "Exactly one Admin 1 loc_id from resolve_points, such as USA-CA. All coordinates in the call must belong to it.",
-  "minLength": 5,
-  "type": "string"
-}
      • addedInput schema / properties / family
        Added value: +{
+  "default": "administrative",
+  "description": "One canonical family ID for the entire batch.",
+  "pattern": "^[a-z0-9_]+$",
+  "type": "string"
+}
      • removedInput schema / properties / include_marine_context
        Removed value: -{
-  "description": "Include parallel Marine overlaps. Defaults to true.",
-  "type": "boolean"
-}
      • changedInput schema / properties / points / description
        Previous value: -"Points already known to fall within admin_1_loc_id. Maximum 100 per call during the initial technical rollout."New value: +"Points already known to fall within the supplied shallow_loc_id scope. Maximum 100 per call during the initial technical rollout."
      • addedInput schema / properties / shallow_loc_id
        Added value: +{
+  "description": "A canonical Admin 1-3 loc_id returned by resolve_points. All coordinates in the call must belong to its scope.",
+  "minLength": 5,
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "points",
-  "admin_1_loc_id"
-]New value: +[
+  "points",
+  "shallow_loc_id"
+]
  7. 4 tool updates
    • Addedresolve_deep_point
    • Addedresolve_deep_points
    • Changedresolve_point10 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"
+]
    • Addedresolve_points
  8. 3 tool updates
    • Changedget_catalog1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "packs"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "catalog_version": {
+      "type": "string"
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "generated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "action"
+      ],
+      "type": "object"
+    },
+    "pack_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "packs": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "provenance": {
+      "type": "object"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tool_families": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
    • Changedget_pack1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "pack_id"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "clarification": {
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "material_policy": {
+      "type": "object"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "action"
+      ],
+      "type": "object"
+    },
+    "pack_id": {
+      "type": "string"
+    },
+    "provenance": {
+      "type": "object"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sources": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
    • Changedget_tool_help1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "tool_name"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "access": {
+      "type": "object"
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "examples": {
+      "type": "array"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "important_output_fields": {
+      "type": "array"
+    },
+    "input_schema": {
+      "type": "object"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "action"
+      ],
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "provenance": {
+      "type": "object"
+    },
+    "purpose": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "recommended_next_calls": {
+      "type": "array"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tool_name": {
+      "type": "string"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  9. 1 tool update
    • Changedresolve_point7 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."

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources