Parameter type mismatches still resulting in failed calls as of 4.1.1

[dsarno]

✅ Working Tools:

• manage_scene: All actions work correctly (get_active, get_build_settings)
• manage_editor: All actions work correctly (get_state, get_project_root)
• manage_script: Read action works correctly
• manage_menu_item: List action works correctly
• manage_prefabs: Valid actions work correctly

❌ Parameter Type Issues Found:

• manage_gameobject:
  Boolean parameters like find_all and search_inactive are being passed as strings instead of booleans
  The tool expects search_term for tag searches, not just tag

• manage_asset:
  Integer parameters like page_size are being passed as strings instead of integers

• read_console:
  Integer parameters like count are being passed as strings instead of integers

🔧 Root Cause:
The issue appears to be in the MCP tool parameter validation - the tools are receiving string values when they expect boolean or integer types. This suggests there might be a parameter serialization/deserialization issue in the MCP bridge.
📋 Next Steps:
The parameter type issues need to be fixed in the MCP tool implementations to properly handle string-to-type conversion.

@msanatan, current main fails most of the pytest suite after the type refactoring (likely because tests need to be updated). I already have a fix for the parameter issue in manage_gameobject, but I can't tell if I'm undoing some of what you did to improve the typing. Let me know and I can push a PR to fix these things and you can see if it's the right direction.

[msanatan]

Boolean parameters like find_all and search_inactive are being passed as strings instead of booleans

Does this mean that the model is sending incorrect parameters? If so, that's a good thing right?

The tool expects search_term for tag searches, not just tag

I'm not 100% sure what this means, the description the LLM has never mentioned that 👀

If you're making changes, you're unlikely to be undoing something. That PR essentially put the tool definition from the comment to typed parameters. The typed parameters, specifying which are nullable etc gets them correctly parsed in Windsurf, Gemini CLI etc. So once there are annotated types, it should be fine.

But let me know, from the error summary you shared, it looks like bad input from the model