Loading ToolBench
AI-driven geospatial scene construction in Houdini, over MCP — security-first, data-only.
Server has 5 tools with mixed quality. Two proof-of-concept tools (health, scene_info) have empty schemas and minimal descriptions. Three data-acquisition tools (acquire_terrain, fetch_3dep_tiles, acquire_model) have detailed parameter schemas and descriptions, but lack documented output schemas and error handling guidance. No tool annotations (readOnlyHint/destructiveHint). Naming is verb-noun compliant. Parameter descriptions are present but some lack format constraints (e.g., bbox format, SHA256 validation). No evidence of idempotency guarantees or recovery guidance in error cases.
Download a pinned ONNX model from HuggingFace with integrity verification. Requires repo ID, filename, and SHA256 hash.
Fetch and prepare real-world elevation data for scene construction. Supports multiple DEM sources (3DEP, Copernicus, SRTM, national portals) with configurable resolution and output modes (flat heightfields or ECEF globe tiles).
Fetch USGS 3DEP DEM tiles by bounding box or explicit tile list. Skips tiles already present. Supports dry-run mode to preview availability.
Proof endpoint — returns server health status and version
Proof endpoint — returns current Houdini scene information
health and scene_info have empty input schemas ({}). Descriptions are under 20 chars ('Proof endpoint...'), capping description score at 20.
No output schemas documented for any tool. LLMs cannot infer what fields to expect or plan downstream calls. acquire_terrain, fetch_3dep_tiles, and acquire_model lack return type documentation.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). health and scene_info are read-only but unmarked. acquire_terrain, fetch_3dep_tiles, and acquire_model are WRITE operations but lack destructiveHint or idempotentHint, leaving agents uncertain about retry safety.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | <=2025-11-25 | v2 |
Parameter constraints lack formal specification. bbox is described as '[min_lon, min_lat, max_lon, max_lat]' but no JSON Schema array constraints (minItems, maxItems, items.type). SHA256 is described as '64-char hex' but no pattern regex. LLMs cannot validate these constraints.
No error handling guidance. Tools accept max_bytes, max_tiles, max_side parameters but do not document what happens if limits are exceeded, network fails, or integrity checks fail. No recovery hints for LLMs.