Skip to main content
Glama

DaedalMap Disaster and Geospatial Data

by com.daedalmap

Create loc_id Conversion Job

create_conversion_job

Creates a synchronous v0 user-data conversion job with preserved scalar fields and JSON rows, CSV, JSON Lines, or Parquet output. Hosted service default: 7,500 rows, tuned around a 10-20 second response budget. A direct local-runtime loopback caller has no service item cap; local machine resources are the boundary. Identifier deduplication keeps repeated geography keys efficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iso3No
itemsYesRows to convert; row-level fields may override top-level defaults.
limitNo
quote_idNoQuote id returned by estimate_conversion_job, when available.
min_shareNo
to_systemNoOptional output reference system. Omit to normalize to loc_id.
request_idNoOptional caller-supplied request id for tracing.
from_systemNo
output_nameNo
output_formatNo
geography_bindingNo
target_admin_levelNo
relationship_vintageNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • removedInput schema / properties / bridge_vintage
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / items / items / properties / bridge_vintage
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / items / items / properties / relationship_vintage
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / relationship_vintage
      Added value: +{
+  "type": "string"
+}
  2. Changed14 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "from_system"
+    ]
+  },
+  {
+    "required": [
+      "geography_binding"
+    ]
+  }
+]
    • addedInput schema / properties / bridge_vintage
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / geography_binding
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "country_scope": {
+      "type": "string"
+    },
+    "geo_level": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        }
+      ]
+    },
+    "id_column": {
+      "type": "string"
+    },
+    "mode": {
+      "enum": [
+        "reference",
+        "loc_id"
+      ],
+      "type": "string"
+    },
+    "system": {
+      "type": "string"
+    },
+    "vintage": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "system"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / iso3
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / items / description
      Previous value: -"Rows to convert; each row needs value and may include row_index."New value: +"Rows to convert; row-level fields may override top-level defaults."
    • addedInput schema / properties / items / items / additionalProperties
      Added value: +false
    • addedInput schema / properties / items / items / properties
      Added value: +{
+  "bridge_vintage": {
+    "type": "string"
+  },
+  "data": {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "integer"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": "Original spreadsheet columns to preserve. Column names beginning daedalmap_ are reserved for generated output fields.",
+    "maxProperties": 200,
+    "type": "object"
+  },
+  "from_system": {
+    "type": "string"
+  },
+  "id": {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  "iso3": {
+    "type": "string"
+  },
+  "limit": {
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "min_share": {
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  "row_index": {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  "target_admin_level": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "integer"
+      }
+    ]
+  },
+  "to_system": {
+    "type": "string"
+  },
+  "value": {
+    "description": "Identifier value; keep as a string to preserve leading zeros.",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / items / items / required
      Added value: +[
+  "value"
+]
    • addedInput schema / properties / limit
      Added value: +{
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / min_share
      Added value: +{
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / output_format
      Added value: +{
+  "enum": [
+    "json_rows",
+    "csv",
+    "jsonl",
+    "parquet"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / output_name
      Added value: +{
+  "maxLength": 80,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "from_system",
-  "items"
-]New value: +[
+  "items"
+]
  3. Added

TDQS

C2.9/5.0
Behavior3/5

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

With only readOnlyHint=false in annotations, the description carries most of the behavioral burden. It usefully discloses synchronous execution, a 7,500-row hosted default, a 10–20 second response budget, and identifier deduplication. However, it does not describe output shape, failure behavior, side effects, or any permissions requirements, leaving the picture incomplete.

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?

The description is compact: three sentences with the core operation front-loaded and the scaling constraints after. There is minimal filler, though jargon like 'v0' and 'loopback' slightly reduces accessibility.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 13 parameters, nested objects, an anyOf requirement, and no output schema, the description is far from complete. It does not explain the required items structure, the from_system versus geography_binding choice, row-level overrides, or what the synchronous job returns. An agent would still need substantial schema inference and sibling exploration to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 31%, so the description must compensate, but it names no parameters directly. It alludes to output formats and the row cap, and 'preserved scalar fields' hints at the data parameter, but from_system, geography_binding, to_system, target_admin_level, min_share, quote_id, and others remain unexplained. The description adds little beyond what the schema already exposes.

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 states a specific verb and resource: 'Creates a synchronous v0 user-data conversion job' and enumerates supported output formats, so the operation is identifiable. It is clear but does not explicitly differentiate itself from siblings like estimate_conversion_job or convert_reference; the 'user-data' and 'synchronous' qualifiers only imply a distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives such as estimate_conversion_job or convert_reference. The hosted/local loopback contrast is behavioral scaling context, not a use-case selector. Prerequisites, sequencing, or exclusion conditions are absent.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct scopes with detailed 'Use this' guidance, but a few pairs like get_disaster_link_chain and get_disaster_links_for_event, or query_dataset versus the specialized get_* event tools, could cause momentary confusion. Overall, descriptions mitigate overlap well.

Naming Consistency4/5

The majority follow a consistent verb_noun pattern (check_, compare_, convert_, create_, estimate_, get_, list_, resolve_). Minor exceptions like loc_id_info and query_dataset are acceptable but break the pattern slightly.

Tool Count3/5

28 tools exceed the preferred range, but the broad domain spanning disasters, geospatial geometry, reference conversion, and export jobs justifies many of them. Still, the count feels heavy and might overwhelm agents.

Completeness5/5

The tool surface is remarkably comprehensive: discovery (catalog, pack, geometry catalog), resolution (point, reference, scope), geometry (check, get, compare), conversion (quote, create, status), and disaster events for multiple types. No critical dead ends for the stated domain.

Resources