Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Open a CityJSON file

cityjson_open

Open a CityJSON file by filename, relative path, or full server-visible path; the server snapshots it and returns a filename for use with later tools.

Instructions

Open a CityJSON file from an optional configured project or data folder by filename, relative path, or full server-visible path. The server snapshots the file and returns its filename for later tools.

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": {
      "source": "<source>"
    },
    "name": "cityjson_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesCityJSON filename or relative path in an optional configured data folder, or full server-visible path. For an attached file, use cityjson_upload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / source / description
      Previous value: -"Full server-visible path inside an allowed root. This cannot be a path from a chat attachment."New value: +"CityJSON filename or relative path in an optional configured data folder, or full server-visible path. For an attached file, use cityjson_upload."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose two non-obvious traits: the server snapshots the file, and the return value is a filename used by later tools. It stops short of stating whether the snapshot persists, whether it is read-only, or any error conditions.

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, front-loaded with the action and source options, then the snapshot/return behavior. Every clause adds information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no annotations and no output schema, the description covers what the tool does, where it looks, and what it returns. Missing only error/failure behavior and explicit confirmation that the snapshot does not mutate the original.

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 'source' parameter already documents all three resolution modes, so the description largely restates it. Baseline 3 is appropriate for a fully documented one-parameter schema.

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 (open a CityJSON file) and enumerates the three accepted source forms (filename, relative path, full server-visible path). It separates itself from the upload family implicitly but never names a sibling, which keeps it short of a 5.

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 'optional configured project or data folder' phrasing hints at context, and the schema description routes attached files to cityjson_upload. However, the description itself gives no explicit when-to-use/when-not guidance against the many upload and import siblings (cityjson_import, cityjson_upload_start, etc.).

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