Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Validate CityJSON syntax and schema

cityjson_validate_schema

Validate CityJSON datasets against official schemas, extensions, and structural checks to detect syntax, schema, and extension issues before use.

Instructions

Validate a dataset with the official cjval validator: JSON syntax, CityJSON schemas, extensions and additional structural consistency checks.

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

Input Schema

NameRequiredDescriptionDefault
dataset_idYesFilename returned by cityjson_open, cityjson_import, or a transformation. Internal dataset handles also work for compatibility.
extension_schemasNo

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. It usefully discloses that validation is delegated to the official cjval validator and what categories of problems are checked, which is meaningful context. However, it is silent on whether errors are returned as a list or a pass/fail flag, whether validation is read-only, and how long a large dataset might take.

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 no filler; the validator name and check list are the most useful information and appear immediately. Slight density in the comma list but nothing that should be cut.

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?

No annotations and no output schema, so the description is the only source of behavioral information. It covers what is checked but leaves the caller unsure what a result looks like and how to trigger extension-aware validation, which matters for a two-parameter tool with one undocumented parameter.

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 description coverage is only 50%: dataset_id is documented in the schema, but extension_schemas has no description. The description mentions "extensions" as something validated but never explains that the caller can supply custom extension schema identifiers or paths, so it does not compensate for the 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 names a specific verb (Validate) and resource (a CityJSON dataset) and enumerates the check classes performed: JSON syntax, CityJSON schemas, extensions, and structural consistency. This implicitly distinguishes it from cityjson_validate_geometry (geometry-only checks), though that sibling is never named explicitly.

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 by the enumerated check types — an agent can infer this is the full schema-level check versus the geometry-only sibling, but there is no explicit "use this when..." or "use cityjson_validate_geometry instead for..." statement. No prerequisites (e.g., dataset must be loaded first) are stated.

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