fix_bad_answer — thinkhard.si prompt tools MCP Tool
fix_bad_answer
(fix bad answer) is one of 14 tools on the
thinkhard.si prompt tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fix_bad_answer from your client
- Claude Code thinkhard.si prompt tools fix_bad_answer run in your project directory
- Claude Desktop thinkhard.si prompt tools fix_bad_answer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor thinkhard.si prompt tools fix_bad_answer ~/.cursor/mcp.json
- VS Code thinkhard.si prompt tools fix_bad_answer .vscode/mcp.json
- Zed thinkhard.si prompt tools fix_bad_answer ~/.config/zed/settings.json
- Windsurf thinkhard.si prompt tools fix_bad_answer ~/.codeium/windsurf/mcp_config.json
- Cline thinkhard.si prompt tools fix_bad_answer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI thinkhard.si prompt tools fix_bad_answer ~/.gemini/settings.json
- Grok thinkhard.si prompt tools fix_bad_answer .mcp.json (in your project root)
- ChatGPT thinkhard.si prompt tools fix_bad_answer Settings → Connectors → Advanced → Developer mode
- Claude.ai thinkhard.si prompt tools fix_bad_answer Settings → Connectors → Add custom connector
- LangChain thinkhard.si prompt tools fix_bad_answer pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http prompt-tools https://thinkhard.si/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.