DaedalMap Administrative Boundaries (loc_id to polygon)

List Published Packs or Geographies

get_catalog

Read-onlyIdempotent

Choose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pack for data or get_geography for geometry. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "catalog": "<catalog>"
    },
    "name": "get_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`catalog`	Yes	Required directory selector.

Output Schema

Name	Required	Description	Default
`error`	No
`packs`	No
`detail`	No
`reason`	No
`scopes`	No
`catalog`	No
`families`	No
`guidance`	No
`warnings`	No
`next_step`	No
`pack_count`	No
`provenance`	No
`request_id`	No
`download_url`	No
`generated_at`	No
`clarification`	No
`result_status`	No
`tool_families`	No
`excluded_count`	No
`resolved_query`	No
`catalog_version`	No
`uncertain_count`	No
`uncertain_packs`	No
`free_get_data_policy_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 11, 2026
- addedOutput schema / properties / free_get_data_policy_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / packs / items / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / packs / items / properties
```
Added value: +{
+  "free_get_data_policy": {
+    "enum": [
+      "eligible",
+      "blocked_paid_pack"
+    ],
+    "type": "string"
+  }
+}
```

Changed15 schema fields changedOct 16, 2026

removedInput schema / properties / catalog / default
```
Removed value: -"data"
```

changedInput schema / properties / catalog / description

Previous value: -"Catalog family. The geography facade defaults to geometry; other facades default to data."New value: +"Required directory selector."

removedInput schema / properties / country_scope

Removed value: -{
-  "description": "Optional ISO3 focus for catalog='geometry' with detail='lite'.",
-  "type": "string"
-}

removedInput schema / properties / detail

Removed 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"
-}

removedInput schema / properties / loc_id

Removed 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"
-}

removedInput schema / properties / time_range

Removed 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"
-}

addedInput schema / required
```
Added value: +[
+  "catalog"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "catalog",
-      "detail"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "catalog"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / excluded_count

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / families

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / resolved_query
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / result_status
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / scopes

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / uncertain_count

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / uncertain_packs

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

Changed2 schema fields changedSep 23, 2026

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"
+}

Changed9 schema fields changedSep 21, 2026

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"
-]
```

Changed1 schema field changedSep 13, 2026

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"
+}

First observedJun 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuine context beyond that: the response carries a full catalog download URL, the baseline covers 252 geographic entities to Admin 2, and certain countries automatically yield deeper tiers.

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

Conciseness3/5

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

The core routing information is front-loaded and efficient, but the trailing sentences on the 252-entity baseline, Admin 2 depth, and the country list are verbose scope trivia that do not help an agent decide or invoke. Roughly a third of the text could be cut without loss of call correctness.

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 an output schema present, return-value explanation is unnecessary, and the description covers selection, sibling routing, and geographic coverage. The only shortfall is that the catalog-scope prose is broader than needed for a single-enum tool, but nothing required for correct invocation is missing.

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 coverage is 100% and the enum is documented, so the schema already carries the argument's mechanics. The description still adds real meaning by explaining what each enum value yields — pack IDs for data versus family and scope IDs for geometry — which is not derivable from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('list published pack IDs or family and scope IDs') and ties the catalog argument to what is returned. The opening 'Choose data or geometry to list...' is slightly convoluted, but a reader can still tell this is the enumeration entry point distinct from get_pack and get_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?

It explicitly routes the agent: use catalog=data for pack IDs, catalog=geometry for family/scope IDs, and use get_pack for data or get_geography for geometry. It gives clear positive guidance and an alternative, though it never states when not to call this tool.

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

All DaedalMap Administrative Boundaries (loc_id to polygon) tools Inspect

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.