MCP Novel Game Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| select_storyC | Bind a story to the player and return its opening scene. |
| chooseC | Record player's choice within their selected story. |
| load_scene_imageC | Return the image for the player's current story and scene. Resize and compress until data size <= 1MB. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| narrator_prompt | Single system prompt used by the narrator LLM. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| novelgame://stories |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: selecting a story, recording a choice, and loading a scene image. No overlap in functionality.
All tool names use lowercase with underscores, but the structure varies: 'choose' is a single verb while others follow verb_noun pattern. The inconsistency is minor.
With 3 tools, the server is well-scoped for a simple novel game interface. Each tool serves a clear purpose without unnecessary bloat.
The basic interaction flow is covered, but missing tools like fetching story list, scene text, or saving progress leave notable gaps that agents may need to work around.