Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Triangulate CityJSON

cityjson_triangulate

Triangulate CityJSON dataset surfaces using cjio; enable sloppy mode only as a fallback when robust triangulation fails.

Instructions

Triangulate surfaces with cjio. Use sloppy=true only when the robust triangulator fails.

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

Input Schema

NameRequiredDescriptionDefault
sloppyNo
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?

No annotations are supplied, so the description carries the full burden. It does not say whether triangulation mutates the dataset in place or produces a new dataset handle, whether it is reversible, whether textures/materials survive it, or how expensive it is — critical omissions for a geometry-mutating operation.

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 short sentences, action first and parameter caveat second, with no redundant restatement of the name or title. Nothing could be removed without losing information.

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

Completeness2/5

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

With no annotations and no output schema, the definition should cover mutation semantics and result handling, and it does neither. For a geometry-rewriting tool the agent is left guessing whether the dataset_id stays valid after the call and what the response looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: dataset_id is documented in the schema, while sloppy has no schema description. The description compensates by explaining what sloppy means functionally (a less robust fallback path) and when to enable it, which is meaningful context beyond the boolean default.

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 and resource ('Triangulate surfaces') and identifies the underlying engine ('with cjio'), so an agent knows exactly what operation is performed. It does not, however, distinguish this tool from neighbors that also alter geometry (e.g. cityjson_clean_vertices, cityjson_filter_lod), so sibling differentiation is absent.

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?

There is one explicit conditional: 'Use sloppy=true only when the robust triangulator fails', which correctly frames sloppy as a fallback. However, there is no guidance on when triangulation itself is needed versus other geometry operations, and no prerequisites (e.g. valid geometry, suitable LoD) are stated.

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