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