DaedalMap Geography Tools (loc_id)

Identify One Identifier Column's Reference System

identify_reference_system

Read-onlyIdempotent

Identify one selected identifier column within one required ISO3 country, GLOBAL, or MARINE scope. Pass bounded strings preserving leading zeros. It checks maintained identifier evidence, not dataset columns or polygons. Ambiguous systems stay unselected until expected.system is supplied. Use identify_dataset_geography first when the column is unknown. No payment required.

Input Schema

TableJSON Schema

Name	Required	Description
`expected`	No
`identifier`	No	One geography identifier to inspect.
`request_id`	No	Optional caller-supplied request id for tracing.
`identifiers`	No	A bounded representative identifier sample. Duplicate values are checked once. Values must be strings so leading zeros are preserved.
`country_scope`	Yes	Required single ISO3 country, GLOBAL, or MARINE scope. Missing scope fails before identifier reads.
`dataset_context`	No	Bounded, non-row dataset clues used to rank plausible interpretations without replacing exact identifier verification.
`validation_scope`	No	Describes whether the bounded input is a sample or, only when it fits the identification cap, the complete distinct-key set. This tool validates every supplied identifier; create_conversion_job validates every row in the full dataset.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`limit`	No
`reason`	No
`status`	No
`batch_id`	No
`guidance`	No
`warnings`	No
`next_step`	No
`candidates`	No
`request_id`	No
`column_count`	No
`clarification`	No
`meter_receipt`	No
`review_required`	No
`identifier_count`	No
`coordinate_binding`	No
`settlement_receipt`	No
`recommended_binding`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

changedInput schema / properties / country_scope / description

Previous value: -"Optional ISO3 country hint used to narrow candidate banks."New value: +"Required single ISO3 country, GLOBAL, or MARINE scope. Missing scope fails before identifier reads."

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

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "status",
+        "candidates"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "batch_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "candidates": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "column_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "coordinate_binding": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "identifier_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "limit": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "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"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "recommended_binding": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "review_required": {
+      "type": "boolean"
+    },
+    "settlement_receipt": {
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / validation_scope / description

Previous value: -"Describes whether the supplied identifiers are a sample or the complete distinct-key set. The tool validates every supplied identifier."New value: +"Describes whether the bounded input is a sample or, only when it fits the identification cap, the complete distinct-key set. This tool validates every supplied identifier; create_conversion_job validates every row in the full dataset."

Changed2 schema fields changedSep 8, 2026

addedInput schema / properties / dataset_context

Added value: +{
+  "additionalProperties": false,
+  "description": "Bounded, non-row dataset clues used to rank plausible interpretations without replacing exact identifier verification.",
+  "properties": {
+    "column_name": {
+      "type": "string"
+    },
+    "column_names": {
+      "items": {
+        "type": "string"
+      },
+      "maxItems": 1000,
+      "type": "array"
+    },
+    "file_name": {
+      "type": "string"
+    },
+    "local_format_match_rate": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "row_geography": {
+      "description": "Optional plain-language clue such as county, tract, or ZIP area.",
+      "type": "string"
+    },
+    "sheet_name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / expected / properties / system / description

Previous value: -"Expected reference system, such as us_census_geoid, loc_id, zcta, or a catalog reference system."New value: +"Caller-declared reference system, such as us_census_geoid, loc_id, zcta, or a catalog reference system. Supply it immediately when known, or after choosing an identification result."

AddedAug 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world. The description adds real context beyond that: it checks 'maintained identifier evidence, not dataset columns or polygons,' explains the ambiguous-unselected behavior, and notes 'No payment required' (a cost trait). It stops short of richer output/timing detail, but the additions are substantive.

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?

Five sentences, front-loaded with purpose and scope before routing and behavior. Each sentence carries information, though the leading-zero instruction mildly duplicates 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 an output schema present, return values need not be explained, and the annotations cover the safety profile. The description covers scope, routing, ambiguity handling, and cost, leaving only minor gaps around pagination/timing that are not essential 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 86%, so the schema already documents nearly all parameters (including the leading-zero string requirement and expected.* fields). The description's 'Pass bounded strings preserving leading zeros' largely restates the schema, adding little beyond the baseline when structured data does the heavy lifting.

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 (identify) and resource (one identifier column's reference system) with explicit scope constraints (one ISO3 country, GLOBAL, or MARINE). It also distinguishes itself from siblings by naming identify_dataset_geography, so an agent can route 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?

Gives an explicit prerequisite/alternative: 'Use identify_dataset_geography first when the column is unknown,' plus a conditional behavior ('Ambiguous systems stay unselected until expected.system is supplied') that tells the agent exactly what to do on an inconclusive result. Nothing is left to inference.

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

All DaedalMap Geography Tools (loc_id) 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.