client-side tools shadowing server-side tools and other thoughts

[runyaga]

There are a number of cases re: AG-UI that need to be specified:

• What happens if a client-side tool shadows a server-side tool?
  • CoPilotkit fails with a "client side tool shadows a registered server side tool" !SHOWS INTERNAL INFO?!?!
• What if a client-side tool has excessive registrants? Should we filter that server-side in a room?
• Should there be a convention adopted so we can discriminate what is client from server side based on function name? e.g. agui_$toolname

[frapell]

The backend is leaking out information like this

The AG-UI frontend tools defines a tool whose name conflicts with existing tool from HTTP_MCP_Client_Toolset(url='https://server.smithery.ai/@smithery-ai/national-weather-service/mcp?api_key=XXXXXXXXXXXXXXXXXXXXXXXXXXXXx&profile=ZZZZZZZZZZZ'): 'get_current_weather'. Rename the tool or wrap the toolset in a `PrefixedToolset` to avoid name conflicts.

[runyaga]

@seb it appears that copilotkit will throw exception if you shadow a server tool; i dont know if this is cause in the dart sdk but this should be handled and gracefully shown to our user