Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Upgrade CityJSON

cityjson_upgrade

Upgrade older supported CityJSON files to the version supported by the installed cjio; provide a dataset ID from open, import, or transformation operations.

Instructions

Upgrade an older supported CityJSON file to the version supported by the installed cjio.

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>"
    },
    "name": "cityjson_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.1/5.0
Behavior2/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, yet it never says whether the upgrade mutates the referenced dataset in place, produces a new dataset_id, or leaves the original intact. It also omits whether the call fails on already-current files and what error or return the agent should expect after a mutation-style operation.

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?

A single front-loaded sentence with no filler; the key constraint (older supported version) appears before the target version. It is arguably terse to a fault, but nothing is wasted or buried.

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?

With no annotations, no output schema, and a write-like operation, the definition leaves the agent guessing about the outcome: in-place mutation versus new dataset handle, preservation of the source file, and failure behavior. For an upgrade/migration tool that is a meaningful completeness gap.

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 100% and the single dataset_id parameter is fully documented in the schema, including its origin from cityjson_open/import and handle compatibility. The description adds no further semantics about that parameter, so the baseline of 3 applies when the schema does the work.

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 names a specific verb and resource ('Upgrade ... CityJSON file') and bounds the scope to 'older supported' inputs targeting the version of the installed cjio. That is enough to distinguish it from validation, export, save, or format-conversion siblings, though no sibling is named explicitly.

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?

Use is implied by the phrase 'older supported CityJSON file', which tells the agent this is for outdated data rather than fresh imports. However, there is no explicit when-not guidance, no mention of what to do for unsupported versions, and no stated alternative such as re-importing the source.

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