Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Create CityJSON subset

cityjson_subset

Create a derived CityJSON subset by IDs, bounding box, radius, random count, or CityObject types; returns a new filename for the filtered dataset.

Instructions

Create a derived CityJSON subset with cjio using IDs, bbox, radius, random count or CityObject types. 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_subset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
bboxNo2D bbox [minX, minY, maxX, maxY] in the dataset CRS.
typesNo
radiusNo
randomNo
excludeNo
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.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does usefully state that the output is a derived dataset plus a new filename, implying the source dataset is not destroyed, but it is silent on whether selectors combine or are mutually exclusive, what happens when nothing matches, and what 'exclude' inverts.

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 sentences, front-loaded with the action and followed immediately by the return value. 'with cjio' is implementation detail, but it is short and the rest of the text earns its place with no redundancy.

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 7-parameter, mutation-style operation with no annotations and no output schema, the description covers the return value ('a new filename') but leaves selector interaction rules and the non-destructive guarantee implicit. It is adequate to attempt a call but not complete enough to guarantee a correct one.

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 only 29% across 7 parameters, so the description must compensate. It does name five of the seven selector parameters (ids, bbox, radius, random, types), which adds meaning over their bare types, but it never explains 'exclude', the mutual exclusivity of selectors, or the required dataset_id contract.

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+resource ('Create a derived CityJSON subset') and enumerates the five selection modes (IDs, bbox, radius, random count, CityObject types). It is clear what the tool produces, though it does not name any sibling it supersedes or contrasts with, so an agent must infer the boundary against cityjson_filter_lod or cityjson_query.

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?

The enumeration of selection criteria implies the situations the tool is for, but there is no explicit when-to-use / when-not-to-use framing and no named alternative. An agent can guess that this is the extraction tool, but cannot tell from the text whether it should prefer this over cityjson_query or cityjson_filter_lod.

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