mcp-rpg-worldstate
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_worldsA | List compact save-game entries. Use this first in a new chat; it never loads full world data. |
| create_worldB | Create an isolated RPG world/campaign. Description holds its durable tone, setting, rules and boundaries as free text. |
| update_worldB | Update a world's durable framing. Do not record transient narration here. |
| delete_worldA | Permanently delete a world and all related entities, scenes, checkpoints and events. Requires exact confirmation 'DELETE: '. |
| apply_world_changesA | Create, update or delete several durable entities atomically in one call. Create operations may define local refs used by locationRef or parentRef, including forward references. Store only lasting or story-relevant changes, preferably together at natural story boundaries. |
| search_entitiesB | Targeted lookup. Supports questions such as all characters in a world, where a character is, or which characters are at a location. |
| set_current_sceneA | Record the compact immediate scene in one operation. Participants describe who is narratively present; this does not move every character permanently. |
| get_world_overviewA | Load a token-conscious save preview. The latest checkpoint contains only playerRecap by default; GM notes and other secret records require explicitly authorized secret access. |
| get_current_contextA | Load world framing plus current scene, its location, characters currently assigned there and active plots. Use after the compact overview when continuing play. |
| create_checkpointA | Create a checkpoint with strictly separated player-safe recap and optional GM-only notes. The server does not classify or rewrite content; entities and events remain authoritative. |
| get_recent_eventsA | Read a compact newest-first history explaining how the authoritative current state developed. Supports backward pagination and events since a checkpoint; do not use it instead of current context. |
| list_checkpointsA | List player-safe checkpoint recaps newest first. GM notes remain absent unless includeSecrets is explicitly true in an authorized GM context. |
| random_numbersA | Generate random integers for unbiased narrative decisions. This is not a rules or dice system. |
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 13 tools
Each tool has a clear, distinct purpose with carefully worded boundaries (e.g., get_current_context vs. get_world_overview vs. get_recent_events). The descriptions are detailed enough that an agent should select correctly, though the overlapping 'get' cluster and create/update endpoints could still cause occasional confusion.
The server consistently uses a snake_case verb_noun pattern (create_world, update_world, search_entities, set_current_scene) that makes behavior predictable. The one outlier, random_numbers, breaks the verb-first pattern but is still clear and descriptively named.
13 tools is well within the ideal range for a domain of this scope. The server covers the full CRUD lifecycle for worlds, plus checkpoints, entities, scenes, and context management without accidental bloat or missing essentials.
The toolset provides comprehensive coverage of the worldstate domain, including world lifecycle, checkpoints, entity search, scene management, and history navigation. It could be even more complete with granular entity-level operations, but the atomic apply_world_changes and search_entities cover most reasonable workflows.