Build and query a structured catalog of installations/AOIs with distance, sector, and coverage queries.
Single tool 'basemap_scan' has a basic description (89 chars) but critically lacks parameter descriptions. The input schema defines 'target' as a string with a description, but the tool description itself is generic and does not explain when to use it, what it returns structurally, or how to interpret results. No output schema is documented. The tool name follows verb_noun convention (scan), but the description does not guide LLM selection or explain prerequisites. No error handling guidance, no pagination, no structured output documentation.
Build and query a structured catalog of installations/AOIs with distance, sector, and coverage queries.. Returns JSON findings.
Parameter 'target' lacks description in tool definition. LLMs cannot infer whether this expects a file path, directory, URL, or project identifier.
No output schema documented. Tool returns JSON findings but LLMs have no visibility into the structure (fields, types, nesting). This prevents downstream tool chaining and forces LLMs to guess field names.
Tool description (89 chars) is generic and does not explain WHEN to use it, WHAT it scans for, or HOW to interpret results. 'Build and query a structured catalog...' is vague about the actual scanning behavior (looks for TODO/FIXME/XXX markers in code).
No error handling guidance. Tool may fail on invalid paths, permission errors, or large directory trees, but provides no recovery hints or error classification for LLMs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. This is a hard architectural limitation.