Configurable tool name mapping or automatic sanitization

[NaqibAhmad]

The 21st.dev Magic MCP server exposes tools like 21st_magic_component_builder which fail with Kimi API because function names must start with a letter/underscore. I have added client-side name sanitization (e.g., prepend n or _ to non-compliant names) before sending to the API, similar to how Gemini CLI handles this. I would like to create a contribution PR for this issue. I have tested on my system and it is working perfectly fine.