DaedalMap Geography Tools (loc_id)

Choose Geography Columns From a Dataset

identify_dataset_geography

Read-onlyIdempotent

Fast structural column selector: pass bounded named columns to find recognized geography headers or latitude/longitude pairs. It does not infer a country, level, or identifier system, open country indexes, or validate values. If more than one column is plausible, select one; then call identify_reference_system with the selected identifier column and one country_scope. No payment required.

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": {
      "columns": "<columns>"
    },
    "name": "identify_dataset_geography"
  }
}

Input Schema

Name	Required	Description
`columns`	Yes	Structurally filtered columns with deterministic representative scalar values. Do not pre-label their geographic system.
`request_id`	No
`country_scope`	No	Optional caller-declared ISO3 country, passed through to the selected column.
`dataset_context`	No

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.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / country_scope / description

Previous value: -"Optional caller-declared ISO3 hint. Omit when unknown."New value: +"Optional caller-declared ISO3 country, passed through to the selected column."

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

AddedSep 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: bounded representative values, no validation of values, no index opening, and no payment. It does not explain result shape or what happens on multiple matches beyond the 'select one' instruction, so the addition is solid but not rich.

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?

Four tight sentences, front-loaded with what the tool does and immediately followed by boundaries and the next-step routing. Nothing is padded except possibly the closing 'No payment required', which is short enough not to hurt.

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?

An output schema exists, so return values need no explanation, and the chaining to identify_reference_system covers the main follow-on decision. The gaps are minor: request_id and dataset_context semantics are left entirely to the schema, and the multi-match behavior is only loosely specified.

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 50% schema coverage the description must carry weight, and it does: 'bounded named columns', 'deterministic representative scalar values', and the instruction not to pre-label the geographic system clarify the required columns payload in ways the schema does not. The country_scope explanation duplicates the schema's own text, and request_id and dataset_context receive no mention in the description.

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 first sentence gives a specific verb and resource ('structural column selector ... find recognized geography headers or latitude/longitude pairs') and the next sentence draws a clear boundary around what it does not do (no country/level inference, no index opening, no value validation). This is enough for an agent to distinguish it from siblings like resolve_point or identify_reference_system without opening any 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?

It gives explicit disambiguation and chaining guidance: 'If more than one column is plausible, select one; then call identify_reference_system with the selected identifier column and one country_scope.' What is missing is any statement of when not to reach for this tool versus siblings that resolve points or bboxes, so it is clear context without full exclusions.

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.