daedal-map

Overview Schema Source Related Servers Discussions Admin

Identify One Identifier Column's Reference System

identify_reference_system

Read-onlyIdempotent

Detects the reference system for a selected identifier column in an ISO3, GLOBAL, or MARINE scope by checking maintained identifier evidence; ambiguous matches need expected.system.

Instructions

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

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

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 changedv1.0.3Nov 12, 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 changedv1.0.1Sep 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"
+}

AddedSep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description nonetheless adds meaningful context: no payment required, ambiguous results are withheld rather than guessed, and the check operates on 'maintained identifier evidence, not dataset columns or polygons.' Return shape is covered by the existing output schema, so no penalty there.

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?

Six short sentences, front-loaded with the core action and scope before the routing and ambiguity notes. The closing 'No payment required' is somewhat tangential, and the leading-zero advice duplicates the schema, but overall there is little wasted text.

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 7-parameter tool with a nested expected object and anyOf identifier/identifiers requirement, the description supplies the scope constraint, ambiguity handling, routing to a sibling, and cost information, while the output schema covers returns. Only the distinction from conversion-oriented siblings is left implicit.

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?

With schema description coverage at 86%, the baseline is 3. The description restates parameters rather than extending them ('bounded strings preserving leading zeros' and the ISO3/GLOBAL/MARINE scope echo the schema verbatim), and only the expected.system escalation path is genuinely reinforced rather than repeated.

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 a precisely bounded resource ('one selected identifier column' within 'one required ISO3 country, GLOBAL, or MARINE scope'), and it names identify_dataset_geography as the sibling it is not. An agent can distinguish it from convert_reference or get_loc_id_info 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: 'Use identify_dataset_geography first when the column is unknown,' and clarifies the ambiguity path (systems stay unselected until expected.system is supplied). It does not, however, contrast itself with other plausible alternatives such as convert_reference or get_loc_id_info, so coverage is clear but not exhaustive.

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

Deploy Server