Unity CLI Loop defines 5 tools with schemas and descriptions, but quality is inconsistent. Tool names lack clear action verbs (hello-world, get-project-info use hyphens; naming convention is weak). Descriptions are present but generic (avg ~80 chars, below 194-char baseline). Schemas vary: hello-world has good parameter detail with enums; get-project-info has empty properties (no params documented); find-game-objects and get-hierarchy have reasonable schemas; hot-reload schema is sparse. No output schemas documented for any tool. Error handling, recovery guidance, and parameter validation rules are absent. No evidence of idempotency hints, permission gates, or audit trail patterns. Tools appear to be inferred from test files rather than explicit MCP registration.
Find Game Objects Tool - searches for GameObjects in the scene by name pattern, components, tags, and layers
Get Hierarchy Tool - exports the scene hierarchy to a file with configurable depth and component inclusion
Project information retrieval custom tool. Example of retrieving detailed Unity project information
Hello World custom tool - Type-safe implementation using Schema and Response. Basic implementation example of a custom tool with strongly typed parameters and response
Hot Reload Tool - applies hot-reload changes to C# code without full recompilation, with status and revert capabilities
get-project-info has empty input schema (no properties defined). Tool is non-functional for LLM parameter binding.
No output schemas documented for any tool. LLMs cannot infer response structure, forcing unstructured parsing and increasing hallucination risk.
Tool names use hyphens (hello-world, get-project-info) instead of underscores (hello_world, get_project_info). Inconsistent with 90% of production tools and MCP conventions.
Descriptions are generic and lack WHEN/WHY context. E.g., 'Project information retrieval custom tool' (50 chars) does not explain when to call it vs alternatives or what fields it returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
hot-reload tool accepts file paths and modifies code without dry-run or confirmation step. Destructive operations should support confirmation pattern to prevent accidental code corruption.