zork-mcp
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_gamesA | List the text-adventure games available to play. |
| start_gameB | Start (or restart) a text-adventure game. The AI is the player — explore with 'look', move with 'go north' etc., take items, and collect treasures to win. |
| actA | Send a command to the current game: move, look, take, use, examine... Returns the game's response. |
| hintA | Get a hint for the current room. |
| scoreA | Show your current score, treasures collected, and move count. |
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 5 tools
Each tool has a clearly distinct purpose: listing games, starting a game, issuing commands, getting hints, and viewing score. No two tools overlap in functionality.
All tool names are single verbs that directly describe their action: list, start, act, hint, score. This is a consistent and predictable pattern.
Five tools is well-scoped for a text-adventure MCP server. Each tool serves a necessary function in the gameplay loop without redundancy.
The core game lifecycle is covered: discover, start, play, assist, and track progress. Minor features like saving/loading are missing but not essential for basic play.