Generate 3D-printable topographic shadow boxes from area bounds, OSM features, and GPX tracks.
This server demonstrates solid foundational tool design with clear verb-noun naming and mostly complete parameter schemas. However, it suffers from significant gaps in output schema documentation, parameter descriptions that lack depth, and error handling that provides minimal recovery guidance. All 18 tools are explicitly registered with descriptions and input schemas visible in tools.go, but descriptions are often terse (10-50 chars) and lack the context needed for LLM selection. Parameter descriptions are present but minimal. Critically, there is NO documented output schema for any tool, LLMs cannot determine what fields to expect or how to chain tool calls. Error handling returns generic text without categorization or recovery hints. The server targets a narrow domain (3D topographic model generation) which reduces the need for complex composition, but the fundamental definition gaps would prevent confident use in a production agent.
Export the generated model to 3MF format (suitable for 3D printing).
Export the generated model to OpenSCAD format for further editing.
Export the map insert to SVG format.
Fetch elevation grid for the currently configured bounds.
Fetch OSM feature overlays: roads, water, buildings.
Generate a 2D map insert showing the area with features.
Generate 3D mesh from elevation and feature data.
No documented output schemas for any tool. LLMs cannot determine what fields to expect in responses, preventing them from planning multi-step tool chains or extracting required data for downstream calls.
Parameter descriptions are minimal (10-50 chars) and lack actionable context. E.g., 'Radius in meters' for radius_m does not explain valid range, whether negative values are rejected, or typical usage (100m to 100km). LLMs cannot validate inputs without these constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 53 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 19 | - | v1 |
Search place name and set area (auto-select on single result).
Return current in-memory session status.
Load a previously saved session state from a JSON file.
Open or refresh local 3D preview at http://localhost:3333.
Save the current session state to a JSON file.
Select one pending geocode candidate and set area.
Set area by center+radius or explicit bounding box.
Set area from GPX file bounds (+ optional padding).
Set colors for terrain, roads, water, buildings, and GPX track.
Set model parameters: width, vertical scale, base height, and shape.
Validate currently selected area and report warnings.
Tool descriptions lack context for LLM selection. E.g., 'Return current in-memory session status' does not explain what status fields mean, when to call it (before/after data fetch?), or how it differs from validate_area. Descriptions should be 50-200 chars and answer: What? When? Prerequisites?
Error responses provide no recovery guidance. E.g., set_area_from_coordinates returns 'Provide either lat/lon/radius_m or north/south/east/west.' but does not explain which is preferred, or include examples of valid calls. Errors should classify as retryable/user-fixable/fatal and guide next steps.
geocode_place returns candidate list in an error response rather than a structured result. This forces LLMs to parse unstructured text (lines with '1. Name (lat, lon) type=...') instead of receiving a typed array. When multiple results exist, return {status: 'multi_result', candidates: [{name, lat, lon, type}, ...]}.
No parameter constraints declared for color values or enum-like fields. E.g., set_colors accepts 'terrain', 'roads', etc. as parameter names but does not validate inputs; set_model_params 'shape' parameter should be an enum (square|circle|hexagon|rectangle) but is described as free-form string.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) declared. Agents cannot determine retry safety, export_3mf, generate_model, and save_session appear to modify state but lack destructiveHint; get_status, fetch_elevation should declare readOnlyHint.