Loading ToolBench
Simple HTTP-based Unity Editor integration for AI assistants
15 tools with complete schemas and descriptions, but quality is uneven. Naming follows verb_noun convention (script_create, folder_delete). Descriptions are present but generic, most lack context on WHEN to use the tool or what happens on failure. Parameters are typed but lack constraints (enums, ranges, patterns). No output schemas documented. Error handling is absent, tools do not guide recovery. Security concerns: destructive operations (script_delete, folder_delete) lack confirmation patterns. Composition is reasonable (single responsibility per tool), but no pagination or result limits documented for folder_list.
Create a new folder in Unity project
Delete a folder from Unity project
List contents of a folder in Unity project
Move a folder to a new location in Unity project
Rename a folder in Unity project
Get comprehensive Unity project information including render pipeline details, project path, Unity version, and platform info
Check Unity MCP server connection status (simple connectivity test only)
No output schemas documented. LLMs cannot plan downstream calls or extract required fields (e.g., what does project_info return? Does folder_list return file counts?). Baseline: 100% of A+ tools document return types.
Destructive operations (script_delete, shader_delete, folder_delete) lack confirmation or dry-run patterns. Agents can irreversibly delete files without safeguards. No error guidance on recovery.
Descriptions are generic and lack context. Most are 50 chars or less (e.g., 'Read a C# script from Unity project'). No guidance on WHEN to use each tool, prerequisites, or what happens on failure. Baseline: A+ tools average 194 chars with actionable context.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Apply a unified diff to a C# script
Create a new C# script in Unity project
Delete a C# script from Unity project
Read a C# script from Unity project
Install/update Unity MCP bridge scripts to a Unity project (works even if Unity server is not running)
Create a new shader in Unity project
Delete a shader from Unity project
Read a shader from Unity project
Parameters lack constraints. 'path' and 'folder' accept free-form strings with no validation rules, patterns, or examples. No enums for constrained values. LLMs will pass invalid paths.
No error handling or recovery guidance. Tools do not return actionable error messages (e.g., 'File not found. Check path syntax: Assets/Scripts/MyScript.cs'). Agents cannot self-correct on failures.