Fatebook MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FATEBOOK_API_KEY | Yes | Your Fatebook API key (required for accessing the Fatebook API) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_questionsB | List Fatebook questions with optional filtering Returns a list of Question objects. By default returns core fields only. Set detailed=True to include all available fields (forecasts, comments, etc.). |
| get_questionC | Get detailed information about a specific Fatebook question Returns a structured Question object with all available fields. |
| resolve_questionC | Resolve a Fatebook question with YES/NO/AMBIGUOUS resolution |
| create_questionC | Create a new Fatebook question |
| add_forecastC | Add a forecast to a Fatebook question |
| add_commentC | Add a comment to a Fatebook question |
| delete_questionC | Delete a Fatebook question |
| edit_questionC | Edit a Fatebook question |
| count_forecastsC | Count forecasts for a specific user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific actions on Fatebook questions or related entities. There is no overlap in functionality, with tools for creating, editing, deleting, getting, listing, resolving questions, and adding comments or forecasts, all well-separated.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_question, add_comment, and resolve_question. This uniformity makes the tool set predictable and easy to understand for an agent.
With 9 tools, the server is well-scoped for managing Fatebook questions, covering core operations like CRUD, listing, resolving, and adding forecasts/comments. Each tool serves a clear purpose without redundancy, fitting the domain appropriately.
The tool set provides complete coverage for the Fatebook question domain, including full CRUD operations (create, get, edit, delete), listing with filtering, resolution, and auxiliary actions like adding comments and forecasts. No obvious gaps exist for typical agent workflows.