17-0 MCP 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": 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. (17-0) |
| get_official_linksA | Return the canonical list of official links for 17-0 (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_17_0 | Summarize what the site is, who it's for, and how it works. — 17-0 |
| plan_a_run_17_0 | Plan a single play-through using verified rules and entry points. — 17-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 address entirely different concerns: one provides game rules and roster constraints, the other provides official links. There is no overlap or ambiguity.
Both tools follow a consistent 'get_' prefix with underscore-separated noun phrases, creating a clear and predictable pattern.
With only 2 tools, the server feels thin for a game-related domain, but it may be intentionally scoped to just rules and links. The count is borderline but not extreme.
The server omits many expected operations for a game site (e.g., game status, player info, leaderboards). The surface is severely incomplete for its implied domain.