cityjson_triangulateTriangulates surfaces in CityJSON datasets with cjio; switch to sloppy mode when the robust triangulator fails.
Triangulate surfaces with cjio. Use sloppy=true only when the robust triangulator fails.
| Name | Required | Description | Default |
|---|---|---|---|
| sloppy | No | ||
| dataset_id | Yes | Dataset handle returned by cityjson_import, cityjson_open, cityjson_import_text, or another transformation tool. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the default is a 'robust triangulator' and sloppy is a fallback, but it does not disclose whether the dataset is modified in place, what is returned, what failure modes exist, or any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler. The first states the tool's purpose, and the second gives conditional parameter guidance. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 description is too thin. It does not explain the return value, whether the operation mutates the input dataset, or how the result fits into the broader cityjson workflow, leaving an agent without enough information to predict the outcome of invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 50%, but the description compensates for the undocumented sloppy parameter by explaining that it should only be used when the robust triangulator fails. dataset_id is already well-described in the schema with its valid sources.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Triangulate surfaces with cjio.' This clearly differentiates the action from related tools such as cityjson_clean_vertices or cityjson_reproject, but it does not explicitly contrast it with any sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when a CityJSON dataset's surfaces need triangulation and gives explicit guidance about when to set sloppy=true. However, it does not state when not to use the tool, mention alternatives, or describe prerequisites beyond what the schema provides.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.