Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Validate CityJSON completely

cityjson_validate

Validate CityJSON datasets by running cjval and val3dity together; returns combined structural and geometric results with invalid object IDs for follow-up.

Instructions

Run cjval and val3dity and return one combined structural + geometric validation result. geometry.reportSummary contains the complete invalidObjectIds list for reliable follow-up subsets.

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_validate"
  }
}

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.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses that two engines run underneath and points to geometry.reportSummary for the complete invalidObjectIds list, which is real value. But it says nothing about whether the dataset is mutated, expected runtime cost of geometric validation, or failure behavior on malformed input.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding, and the core action plus its engine composition are front-loaded. The second sentence earns its place by warning where the untruncated ID list lives.

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?

There is no output schema, so the description must convey the return shape, and it only describes one nested field path (geometry.reportSummary.invalidObjectIds). The structural half of the combined result is left undescribed, leaving the agent to discover the rest of the payload by calling it.

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 100% and the single dataset_id parameter is already documented in the schema, including the provenance of the value ('Filename returned by cityjson_open...'). The description adds no additional meaning about the identifier, so the baseline of 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?

The description names a specific verb ('Run cjval and val3dity') and resource ('structural + geometric validation'), and the word 'combined' implicitly positions it as the superset of cityjson_validate_schema and cityjson_validate_geometry. It stops short of naming those siblings, so an agent must infer the distinction from the adjective alone.

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?

Usage is only implied: 'one combined ... result' suggests this is the full check versus the narrower sibling validators, and the follow-up mention hints at subsetting invalid objects. There is no explicit when-to-use/when-to-prefer-a-sibling statement or cost warning for running both engines.

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