Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Filter CityJSON LoD

cityjson_filter_lod

Filter CityJSON datasets to retain only one specified level of detail; returns a new filename for the filtered result.

Instructions

Keep only one level of detail using cjio lod_filter. 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>",
      "lod": "<lod>"
    },
    "name": "cityjson_filter_lod"
  }
}

Input Schema

NameRequiredDescriptionDefault
lodYes
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 provided, so the description carries the full behavioral burden. It discloses only that a new filename is returned, implying a non-destructive transformation, but says nothing about whether the original dataset remains available, whether the operation can fail on mixed-LoD input, or whether there are performance or size constraints. For a transformation tool with zero annotation coverage, this is a significant gap.

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 core action and followed by the return behavior. There is no wasted wording, though the brevity contributes to the gaps in other dimensions rather than being a structural flaw.

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?

The tool is a dataset transformation with two required parameters, no output schema, and no annotations. The description omits the lod value format, whether the original dataset is preserved, and how the returned filename relates to other sibling tools. It is not complete enough for an agent to call this tool confidently without inspecting the schema and inferring behavior.

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 coverage is 50%: dataset_id is documented in the schema, but lod has no schema description. The tool description does not explain the accepted LoD format (for example '2.2' or '1.2') or whether multiple LoDs can be retained. With half the parameters undocumented and the description adding no parameter meaning, the description fails to compensate for the coverage gap.

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 states a specific verb and resource: keep only one level of detail from a CityJSON dataset, implemented via cjio lod_filter. It also states the result is a new filename, which distinguishes it from in-place transforms. It stops short of differentiating itself from sibling transformations such as cityjson_subset or cityjson_clean_vertices.

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 tool versus alternatives like cityjson_subset (which may also filter by attributes) or the other transformation tools. Prerequisites are unstated, and the agent is not told what happens to the original dataset or whether the output must be fed into a subsequent tool.

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