# MCP usage rules for this workspace

- When this workspace MCP server `mcpHal9002` is available in the tool runtime, use its tools directly instead of calling the local Python module as a fallback.
- Only fall back to local Python entrypoints when the required MCP capability is not exposed in the current tool runtime.
- If a behavior looks inconsistent with the current source code after changes, suspect a stale VS Code MCP process or cached tool schema first.
- In that case, explicitly warn the user that the issue might be caused by VS Code not having restarted or refreshed the MCP server yet.
- Prefer asking the user to run `MCP: List Servers`, restart `mcpHal9002`, or `MCP: Reset Cached Tools` before diagnosing deeper runtime mismatches.