27-0-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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_game_rulesA | Return the verified game rules, roster constraints, and public entry points the site exposes. (27-0) |
| get_official_linksA | Return the canonical list of official links for 27-0 (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_27_0 | Summarize what the site is, who it's for, and how it works. — 27-0 |
| plan_a_run_27_0 | Plan a single play-through using verified rules and entry points. — 27-0 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| rules | Verified game rules, roster-building constraints, and public entry points. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 2 tools
The two tools have distinctly different purposes: one returns game rules, the other returns official links. There is no overlap in functionality.
Both tools follow a consistent 'get_' prefix followed by a noun describing the resource. The naming pattern is uniform.
With only two tools, the server feels minimal. While the tools are appropriate for a simple information retrieval server, the number is at the low end of the acceptable range for a game-related MCP.
The server only provides static information retrieval. For a game MCP, one would expect additional tools for player interaction, game state management, or rule lookup by topic. The lack of such features creates significant gaps.