get_player_complaints — Wieldr game radar MCP Tool Read-only
get_player_complaints
(get player complaints) is one of 13 tools on the
Wieldr game radar
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_player_complaints from your client
- Claude Code Wieldr game radar get_player_complaints run in your project directory
- Claude Desktop Wieldr game radar get_player_complaints ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wieldr game radar get_player_complaints ~/.cursor/mcp.json
- VS Code Wieldr game radar get_player_complaints .vscode/mcp.json
- Zed Wieldr game radar get_player_complaints ~/.config/zed/settings.json
- Windsurf Wieldr game radar get_player_complaints ~/.codeium/windsurf/mcp_config.json
- Cline Wieldr game radar get_player_complaints ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wieldr game radar get_player_complaints ~/.gemini/settings.json
- Grok Wieldr game radar get_player_complaints .mcp.json (in your project root)
- ChatGPT Wieldr game radar get_player_complaints Settings → Connectors → Advanced → Developer mode
- Claude.ai Wieldr game radar get_player_complaints Settings → Connectors → Add custom connector
- LangChain Wieldr game radar get_player_complaints pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http radar https://wieldr.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.