Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Import CityJSON from the input inbox

cityjson_import

Registers a CityJSON file already placed in the configured input inbox and returns its filename, enabling upload-bridge clients such as Datum to import models.

Instructions

Register a CityJSON file already placed in the configured input inbox and return its filename. This is for clients with an upload bridge, such as Datum. If filename is omitted, the inbox must contain exactly one JSON file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cityjson_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNoFilename shown by cityjson_list_imports or supplied by the chat application attachment metadata.
display_filenameNoOriginal user-visible filename when an upload bridge stores the file under a generated name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / display_filename
      Added value: +{
      +  "description": "Original user-visible filename when an upload bridge stores the file under a generated name.",
      +  "maxLength": 255,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses the key precondition (file must already exist in the inbox) and the return value (the filename), but says nothing about what happens on filename collision, whether the file is moved or copied, permissions/configuration requirements, or error behavior when no file or multiple files are present. These are meaningful gaps for a registration mutation.

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?

Three short sentences, front-loaded with the action and return value, followed by the client-type qualifier and the fallback condition. No filler, no redundancy with the title, and each sentence carries distinct information.

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 two-parameter, no-output-schema tool, the description covers purpose, the intended client type, and the single precondition for the optional-parameter path. The remaining gap is failure-mode behavior (collisions, multiple/no files), which an agent would likely need to handle gracefully.

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 100%, so both parameters are already documented, which sets the baseline at 3. The description adds one piece of real semantics beyond the schema: omitting filename requires the inbox to contain exactly one JSON file. It does not mention display_filename, leaving that entirely to the 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?

The description opens with a specific verb and resource: "Register a CityJSON file already placed in the configured input inbox and return its filename." That clearly separates it from the upload family (cityjson_upload, cityjson_upload_start, cityjson_upload_chunk) by placing the file in an inbox rather than transferring bytes. It stops short of naming those siblings explicitly, so the differentiation is implied rather than spelled out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear selection condition: "This is for clients with an upload bridge, such as Datum," which tells an agent when this path applies instead of a direct upload tool. It also states the precondition for omitting filename (exactly one JSON file in the inbox). What is missing is an explicit pointer to the alternative tool for clients without an upload bridge.

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