Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Assign CityJSON CRS

cityjson_assign_crs

Assign or update an EPSG reference to a CityJSON dataset without altering coordinate values, returning a new filename.

Instructions

Assign/update the EPSG reference without changing coordinate values using cjio. 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_assign_crs"
  }
}

Input Schema

NameRequiredDescriptionDefault
epsgYes
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.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two non-obvious behaviors: coordinates are untouched (metadata-only change) and the result is a new filename rather than an in-place mutation of dataset_id. It says nothing about whether the source dataset survives, what happens with an invalid EPSG code, or permission requirements.

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?

Two short sentences with zero filler; the key constraint (no coordinate change) and the return value are both front-loaded and immediately scannable.

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 simple two-parameter tool with no output schema, the description covers the essential contract: it mutates CRS metadata only and returns a new filename. Only error/mutation-safety details are missing, which is a minor gap at this complexity level.

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 50%: dataset_id is documented in the schema, but epsg only has numeric bounds. The description adds that epsg is an EPSG reference applied to the dataset metadata, which partially compensates, but it does not establish expected format (e.g. 7415 vs 'EPSG:7415') or validity constraints.

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?

States a specific verb (assign/update) and resource (the EPSG reference in the dataset), and the clause 'without changing coordinate values' effectively separates it from cityjson_reproject, which does alter coordinates. It stops short of naming the sibling explicitly, so the differentiation is implied rather than stated.

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?

The 'without changing coordinate values' phrasing implies when this is preferred over a reprojection, but there is no explicit 'use this instead of cityjson_reproject when...' guidance, nor any stated preconditions such as requiring an opened dataset.

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