Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Clean CityJSON vertices

cityjson_clean_vertices

Removes duplicate and orphan vertices from a CityJSON dataset and returns a new cleaned filename.

Instructions

Remove duplicate and orphan vertices with cjio vertices_clean. 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>"
    },
    "name": "cityjson_clean_vertices"
  }
}

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.2/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 one important behavioral fact: the operation returns a new filename rather than modifying in place, so it is effectively non-destructive. However, it says nothing about whether the original dataset is discarded, whether the new dataset must be saved/exported separately, or what the return string looks like beyond 'a filename'.

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?

Two short sentences, front-loaded with the action and ending with the return value. Nothing is padded, though the mention of the internal cjio command is mild implementation detail rather than agent-facing guidance.

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 one-parameter, no-annotation, no-output-schema tool this is close to adequate, and the return value is stated. Still missing is pipeline context: whether the result replaces the input handle, and whether the agent should chain into cityjson_save or cityjson_export afterwards.

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 description coverage is 100% and the single dataset_id parameter is already documented in the schema as coming from cityjson_open, cityjson_import, or a transformation. The description adds no further meaning about accepted handle formats or constraints, so baseline 3 applies.

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 (remove duplicate and orphan vertices) and names the underlying operation (cjio vertices_clean). It is clearly distinguishable from siblings like cityjson_remove_textures or cityjson_validate, though it does not explicitly contrast itself with any of them.

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, no preconditions (e.g. run after import/merge, before export), and no statement about how it relates to validate or triangulate. The agent must infer the workflow position entirely.

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