Description
When the Gemini CLI starts with the desktop-commander MCP server enabled, a warning is logged
indicating that the set_config_value tool is being skipped. The reason provided is that the tool's
parameter schema is missing explicit type definitions.
Steps to Reproduce
- Configure the Gemini CLI to use the @wonderwhy-er/desktop-commander MCP server.
- Start the Gemini CLI.
- Observe the startup logs.
Error Message
The following warning is displayed in the console:
1 Skipping tool 'set_config_value' from MCP server 'desktop-commander' because it has missing
types in its parameter schema.
Expected Behavior
The set_config_value tool should be loaded correctly by the CLI without any warnings.
Actual Behavior
The tool is skipped, and the warning message is logged, preventing the tool from being used.
Environment
- OS: Linux
- Desktop Commander Version: latest (as installed via npx @wonderwhy-er/desktop-commander@latest)
Suggested Fix
The issue appears to be in the tool's schema definition within the source code. Adding explicit
types to the parameters for the set_config_value tool would likely resolve this. The schema should
probably define the key parameter as a string and the value parameter with its expected type(s).
Thank you for this great tool
Description
When the Gemini CLI starts with the desktop-commander MCP server enabled, a warning is logged
indicating that the set_config_value tool is being skipped. The reason provided is that the tool's
parameter schema is missing explicit type definitions.
Steps to Reproduce
Error Message
The following warning is displayed in the console:
1 Skipping tool 'set_config_value' from MCP server 'desktop-commander' because it has missing
types in its parameter schema.
Expected Behavior
The set_config_value tool should be loaded correctly by the CLI without any warnings.
Actual Behavior
The tool is skipped, and the warning message is logged, preventing the tool from being used.
Environment
Suggested Fix
The issue appears to be in the tool's schema definition within the source code. Adding explicit
types to the parameters for the set_config_value tool would likely resolve this. The schema should
probably define the key parameter as a string and the value parameter with its expected type(s).
Thank you for this great tool