Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Rename CityJSON attribute

cityjson_attribute_rename

Rename an attribute across all CityObjects in a CityJSON dataset with cjio, enabling consistent schema updates and property changes.

Instructions

Rename an attribute across CityObjects with 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>",
      "old_name": "<old_name>",
      "new_name": "<new_name>"
    },
    "name": "cityjson_attribute_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYes
old_nameYes
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

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden, yet it only implies a mutation via the word "rename." It does not say whether existing attributes on all objects are modified in place, what happens if old_name is absent, whether the change is persisted or in-memory only, or how errors are surfaced.

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 or repetition. It is efficient, though the brevity is partly under-specification rather than disciplined editing.

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 parameterized mutation tool with no annotations, no output schema, and undocumented parameters, the definition is too thin. An agent lacks enough to know whether the rename persists, whether a save step is required, and how failures on missing attributes behave.

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 33% – just dataset_id is documented in the schema, and that text largely references other tools. The description adds nothing about old_name/new_name semantics: no statement on nested or dotted attribute paths, case sensitivity, or whether collisions with an existing new_name are rejected.

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?

"Rename an attribute across CityObjects with cjio" gives a specific verb (rename), resource (attribute), scope (across CityObjects) and engine (cjio). It is clear enough to distinguish from cityjson_attribute_remove by name, but the description itself does no explicit sibling differentiation.

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 when-to-use guidance: nothing says this is a mutation on an already-opened dataset, whether the change must be followed by cityjson_save or cityjson_export, or when to prefer it over cityjson_attribute_remove or a query-based workflow. The agent must infer all preconditions from the sibling list.

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