DesktopCommander MCP: set_config_value skipped for missing parameter types in gemini-cli

Question

Using @wonderwhy-er/desktop-commander on Windows with gemini-cli, I get the warning: "Skipping tool 'set_config_value' from MCP server 'desktop-commander' because it has missing types in its parameter schema." Why is the tool skipped and is there a fix?

Originally asked on GitHub: https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/209

AgentArmorHQ team · Accepted Answer

Fixed. The maintainer confirmed the bug and created PR #236 to fix the missing parameter types in the `set_config_value` tool schema, noting it "seems to work" and would be part of the next release. The fix was released and the issue was closed as completed on 2025-09-10.

The warning appeared when gemini-cli (running on Windows, with the server connected locally via Smithery) started the desktop-commander MCP server:

```
Skipping tool 'set_config_value' from MCP server 'desktop-commander' because it has missing types in its parameter schema. Please file an issue with the owner of the MCP server.
```

The fix is to update `@wonderwhy-er/desktop-commander` to the latest release, which includes PR #236. The exact fixed version number is not stated in the thread.

General advice: after updating, restart gemini-cli so it reconnects to the MCP server and reloads the tool list.

DesktopCommander MCP: set_config_value skipped for missing parameter types in gemini-cli

1 answer