Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Reproject CityJSON

cityjson_reproject

Reproject CityJSON coordinates to a target EPSG CRS when the source file already defines a CRS. Returns a new dataset filename for further processing.

Instructions

Reproject coordinates to a target EPSG CRS with cjio. The source file must already define a CRS. Returns a new filename.

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": {
      "dataset_id": "<dataset_id>",
      "epsg": "<epsg>"
    },
    "name": "cityjson_reproject"
  }
}

Input Schema

NameRequiredDescriptionDefault
epsgYes
digitNo
dataset_idYesFilename returned by cityjson_open, cityjson_import, or a transformation. Internal dataset handles also work for compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / dataset_id / description
      Previous value: -"Dataset handle returned by cityjson_import, cityjson_open, cityjson_import_text, or another transformation tool."New value: +"Filename returned by cityjson_open, cityjson_import, or a transformation. Internal dataset handles also work for compatibility."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the underlying engine (cjio) and that the result is a new artifact ('Returns a new filename'), implying the input dataset is not mutated in place. It stops short of stating failure behavior when no CRS is present, whether intermediate datasets accumulate, or how the new file relates to the original dataset_id.

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?

Three short sentences, front-loaded with the action before the precondition and the return value. Every clause carries information and nothing is redundant.

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

Completeness3/5

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

For a coordinate-transforming mutation tool with no annotations and no output schema, the definition covers the core action, the precondition, and the return shape. It leaves gaps on how the undocumented 'digit' parameter behaves, what happens to the source dataset, and how errors surface when the CRS is missing.

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 coverage is only 33%, so the description must compensate. It effectively explains 'epsg' as the target CRS and hints that 'dataset_id' is a filename handle ('Returns a new filename'), which aligns with the schema note. The 'digit' parameter receives no explanation at all in either the schema or the description, leaving one of three parameters opaque, which caps this below a 4.

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 gives a specific verb and resource ('Reproject coordinates to a target EPSG CRS') and names the engine ('with cjio'), so the operation is unambiguous. It does not explicitly contrast itself with near-siblings like cityjson_assign_crs or cityjson_translate, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

One real prerequisite is stated: 'The source file must already define a CRS,' which tells the agent a precondition for calling. However there is no guidance on when to choose this over cityjson_assign_crs (which sets a CRS) or cityjson_translate (which shifts coordinates), and no mention of what to do if the precondition fails.

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