Skip to content

Commit 4d57cd1

Browse files
authored
Merge pull request #1406 from RizgarOzan/docs/skill-custom-tool-fallback
docs(skill): say where to look when a tool is not in the tool list
2 parents 2fcc179 + 12a1638 commit 4d57cd1

2 files changed

Lines changed: 10 additions & 0 deletions

File tree

.claude/skills/unity-mcp-skill/SKILL.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,11 @@ Before applying a template:
2727
5. Verify results → read_console, manage_camera(action="screenshot"), resources
2828
```
2929

30+
**If a tool you need is not in your tool list, it is not necessarily missing.** Check these before troubleshooting the connection:
31+
32+
- **Project custom tools** (C# `[McpForUnityTool]`): with project-scoped tools enabled on the server, they are *not* callable by name. List them via `mcpforunity://custom-tools` and run them with `execute_custom_tool(tool_name="...", parameters={...})`. With it disabled, they are registered as ordinary tools and appear in your list.
33+
- **Disabled tool groups**: over HTTP, a session starts with only the `core` group enabled. Over stdio, all groups start enabled and are then synced to the tool toggles in the Unity editor, so a tool can still be hidden. `manage_tools(action="list_groups")` shows the groups, `manage_tools(action="activate", group="...")` enables one.
34+
3035
## Critical Best Practices
3136

3237
### 1. After Writing/Editing Scripts: Wait for Compilation and Check Console

unity-mcp-skill/SKILL.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,11 @@ Before applying a template:
2727
5. Verify results → read_console, manage_camera(action="screenshot"), resources
2828
```
2929

30+
**If a tool you need is not in your tool list, it is not necessarily missing.** Check these before troubleshooting the connection:
31+
32+
- **Project custom tools** (C# `[McpForUnityTool]`): with project-scoped tools enabled on the server, they are *not* callable by name. List them via `mcpforunity://custom-tools` and run them with `execute_custom_tool(tool_name="...", parameters={...})`. With it disabled, they are registered as ordinary tools and appear in your list.
33+
- **Disabled tool groups**: over HTTP, a session starts with only the `core` group enabled. Over stdio, all groups start enabled and are then synced to the tool toggles in the Unity editor, so a tool can still be hidden. `manage_tools(action="list_groups")` shows the groups, `manage_tools(action="activate", group="...")` enables one.
34+
3035
## Critical Best Practices
3136

3237
### 1. After Writing/Editing Scripts: Wait for Compilation and Check Console

0 commit comments

Comments
 (0)