Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Import a small CityJSON text document

cityjson_import_text

Imports a small CityJSON document supplied as JSON text, including small chat attachments, into the managed workspace while preserving its original filename. Use it for complete documents; use the upload tool for large or incomplete files.

Instructions

Import a small complete CityJSON document already available as text, including a small chat attachment exposed to the model by the client. Preserve the original filename. For missing, incomplete, or large attachments, use cityjson_upload.

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": {
      "content": "<content>"
    },
    "name": "cityjson_import_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesComplete UTF-8 CityJSON document as JSON text.
filenameNoDisplay filename used for the managed workspace copy.import.city.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavior. It does disclose two useful traits: the original filename is preserved and validation of completeness is the caller's responsibility ('complete' document required). It says nothing about what the import produces, whether it mutates workspace state, or how errors on malformed JSON surface.

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 scope, followed by the preservation behavior and the fallback route. No filler and nothing repeated from the title.

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 import tool with a fully documented schema and no output schema, the description covers what to supply, the size boundary, and where to go otherwise. The remaining gap is what happens after import (does it open, list, return an id), which a sibling like cityjson_list_imports or cityjson_open implies but the description never states.

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 both parameters are described in the schema, including the 200-char cap and default filename, so the baseline is 3. The description adds only the 'complete CityJSON document' requirement for content and the filename-preservation intent, not format details or size limits beyond 'small'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (import a small complete CityJSON document already available as text) plus the scope constraint 'small', and explicitly differentiates from the sibling cityjson_upload for missing/incomplete/large cases.

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

Usage Guidelines5/5

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

Explicitly names the alternative (cityjson_upload) and the exact conditions that select it: missing, incomplete, or large attachments. It also indicates the positive case — a complete document plus a small chat attachment — so routing is unambiguous.

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