Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Remove CityJSON attribute

cityjson_attribute_remove

Remove a named attribute from all CityObjects in a CityJSON dataset. Specify the dataset and attribute name to clean or simplify model data.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
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.9/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 and mostly drops it. It implies an irreversible mutation but never says whether the change is applied in place or returns a new dataset, what happens if the attribute is missing on some CityObjects, or whether the result needs cityjson_save to persist.

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 zero filler, and the target scope is stated before the tooling reference. It is arguably too terse for a mutation, but nothing in it is wasted.

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 destructive mutation with no annotations and no output schema, the description should explain persistence, failure behavior, and the relationship to the sibling rename/remove tools. None of that is present, so an agent would have to guess about side effects.

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, while name has no description at all. The phrase "an attribute" indirectly tells the agent that name is the attribute key, which adds a little meaning, but it does not cover case sensitivity, namespaced/generic attributes, or nested paths.

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-and-resource pair ("Remove an attribute") plus the scope ("across CityObjects") and the underlying engine (cjio). An agent can infer it is the inverse of cityjson_attribute_rename, though the description never names that sibling explicitly.

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 on when to use this versus cityjson_attribute_rename or cityjson_query, no stated prerequisites (e.g. the dataset must be opened first), and no exclusions. Usage must be inferred entirely from the name.

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