Fantasy World MCP Simulator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initializeWorldB | Create a new world simulation. REQUIRED: Include all fields including resources:{} (can be empty). |
| simulateC | Run simulation forward in time |
| getWorldStateC | Get current state of a world |
| getTimelineB | Get timeline of events for a world |
| generateLocationB | Generate a new location (dungeon, city, etc.) based on world context |
| exportWorldC | Export world data in various formats |
| listHeroesA | List all heroes in a world, optionally filtered by status |
| getHeroB | Get detailed information about a specific hero |
| listWorldsA | List all created worlds |
| deleteWorldB | Delete a world |
| loadWorldA | Load a world from previously saved JSON data. Use this when resuming a world from AI context. |
| addPopulationA | Add a new population (including monsters) to an existing world. Use this to add orcs, elves, etc. after world creation. |
| createCraftB | Create a new craft/item/heritage object. AI should generate creative names and descriptions for magical items, weapons, books, artifacts, etc. |
| completeQuestA | Mark a quest as completed or failed. Heroes (AI-controlled) or players can complete quests. |
| assignHeroToQuestB | Assign a hero to an open quest. |
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 15 tools
Each tool targets a distinct resource and action, such as listHeroes vs getHero and assignHeroToQuest vs completeQuest. There is no overlap in functionality.
All tool names follow a consistent verb-first camelCase pattern (e.g., listWorlds, initializeWorld, generateLocation). Even 'simulate' aligns with the verb-first style, and there is no mixing of conventions.
15 tools is within the recommended range and each tool serves a clear purpose in managing the world simulation, from lifecycle operations to content generation and quest handling. No tool is redundant.
The toolset covers world lifecycle well but has significant gaps: no create/list/delete for quests, and locations/crafts have create-only operations without corresponding read tools. Agents must rely on getWorldState to indirectly access these resources.