Skip to main content
Glama

DaedalMap Disaster and Geospatial Data

by com.daedalmap
OverviewDiscussionsAdmin

Get loc_id Geometry

get_geometry
Read-only

Availability check and bounded shape retrieval for exact loc_ids or one administrative scope. Exact selection accepts loc_id or loc_ids. Scope selection accepts parent_loc_id plus admin_level and uses the optimized Admin Spine layout: Admin 0-3 stays on one national bank, while deeper levels require an Admin 1 parent and stay on one deep partition. The default response is the fast preflight: it projects has_shape, shape metadata, centroid, and bounding box without reading polygon coordinates. Set include_polygon=true only when exact coordinates are needed. Independent geometry families are selected by exact loc_ids, not inferred as administrative descendants. Use get_loc_id_info for hierarchy, catalog coverage, or crosswalk details. Historical geometry is returned first and successors are never substituted automatically. No payment required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo
loc_idNoDaedalMap loc_id, such as USA-CA-037, USA-Z-00601, USA-NWSFZ-AKZ317, EEZ-USA, or IHO1953-240001002.
loc_idsNoExact DaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true.
batch_idNoOptional caller-supplied batch id for tracing.
request_idNoOptional caller-supplied request id for tracing.
include_polygonNoWhen true, include the full GeoJSON geometry. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
-  {
-    "required": [
-      "loc_id"
-    ]
-  },
-  {
-    "required": [
-      "loc_ids"
-    ]
-  }
-]
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "required": [
+      "loc_id"
+    ]
+  },
+  {
+    "required": [
+      "loc_ids"
+    ]
+  },
+  {
+    "required": [
+      "scope"
+    ]
+  }
+]
    • removedInput schema / properties / detail
      Removed value: -{
-  "default": "lite",
-  "description": "Lite returns shape metadata, bbox, and centroid. Full also includes the attached location-info block.",
-  "enum": [
-    "lite",
-    "full"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / loc_ids / description
      Previous value: -"DaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true."New value: +"Exact DaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true."
    • addedInput schema / properties / loc_ids / minItems
      Added value: +1
    • addedInput schema / properties / loc_ids / uniqueItems
      Added value: +true
    • addedInput schema / properties / scope
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "admin_level": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        }
+      ],
+      "description": "Descendant level to retrieve, such as admin_2, 2, or county."
+    },
+    "bbox": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "number"
+          },
+          "maxItems": 4,
+          "minItems": 4,
+          "type": "array"
+        },
+        {
+          "type": "string"
+        }
+      ],
+      "description": "Optional minLon,minLat,maxLon,maxLat intersection filter."
+    },
+    "parent_loc_id": {
+      "description": "Administrative parent loc_id, such as USA-TX or CAN-BC.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "parent_loc_id",
+    "admin_level"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "lite",
+  "description": "Lite returns shape metadata, bbox, and centroid. Full also includes the attached location-info block.",
+  "enum": [
+    "lite",
+    "full"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • removedInput schema / properties / include_info
      Removed value: -{
-  "description": "When true for loc_ids batch mode, include heavier loc_id_info enrichment for each result. Default false for lean bulk geometry responses.",
-  "type": "boolean"
-}
  4. Changed1 schema field changed
    • addedInput schema / properties / include_info
      Added value: +{
+  "description": "When true for loc_ids batch mode, include heavier loc_id_info enrichment for each result. Default false for lean bulk geometry responses.",
+  "type": "boolean"
+}
  5. Changed4 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "loc_id"
+    ]
+  },
+  {
+    "required": [
+      "loc_ids"
+    ]
+  }
+]
    • addedInput schema / properties / batch_id
      Added value: +{
+  "description": "Optional caller-supplied batch id for tracing.",
+  "type": "string"
+}
    • addedInput schema / properties / loc_ids
      Added value: +{
+  "description": "DaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "loc_id"
-]
  6. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the readOnlyHint annotation: it explains the default preflight response (shape metadata, centroid, bbox without polygon coordinates), the optional include_polygon for full GeoJSON, that historical geometry is returned first with no automatic successor substitution, and that no payment is required. These are non-obvious behaviors an agent must know to use the tool correctly.

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 well-structured and information-dense without fluff. It front-loads the core purpose, then logically flows through selection modes, default behavior, include_polygon guidance, selection rules, sibling tool reference, historical behavior, and payment status. Every sentence adds value, and the length is appropriate for the tool's complexity.

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?

Given the tool's complexity (multiple selection modes, admin level handling, preflight vs. full polygon, historical handling), the description covers all critical aspects: what the default response contains, when to request polygons, how selection works, which sibling to use for hierarchy, and the historical behavior. The absence of an output schema is compensated by explicit description of the preflight fields. Nothing an agent needs to invoke correctly 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?

With schema description coverage at 83%, the schema already documents most parameters. The description adds contextual meaning: it clarifies that include_polygon is only for exact coordinates, that loc_ids has a configurable cap (lower when include_polygon is true), and it explains the Admin Spine layout for scope selection. These enrich the schema's bare descriptions, earning a score above the baseline.

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

Purpose5/5

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

The description opens with a precise purpose: 'Availability check and bounded shape retrieval for exact loc_ids or one administrative scope.' It clearly identifies the resource (shape geometry) and distinguishes between exact and scope selection modes. It also names a sibling tool (get_loc_id_info) that covers different needs, making it unambiguous which tool to use.

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?

The description provides explicit usage guidance: it states when to use exact vs. scope selection, when to set include_polygon (only when exact coordinates are needed), and explicitly tells the agent to 'Use get_loc_id_info for hierarchy, catalog coverage, or crosswalk details.' It also notes that independent geometry families must be selected by exact loc_ids, not inferred, preventing misuse.

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

All DaedalMap Disaster and Geospatial Data toolsInspect
Try in Browser
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