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