7-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 |
|---|---|
| list_scenariosA | Return the canonical list of game modes and scenarios the site exposes (free play, daily, leaderboards, etc.). (7-0) |
| get_official_linksA | Return the canonical list of official links for 7-0 (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_7_0 | Summarize what the site is, who it's for, and how it works. — 7-0 |
| plan_a_run_7_0 | Plan a single play-through: pick a mode, draft a roster strategy, and predict outcomes. — 7-0 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| scenarios | Available game modes, scenarios, and roster-building constraints. |
| 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 lists game scenarios, the other returns official links. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern with underscores: list_scenarios and get_official_links.
With only 2 tools, the server feels minimal. While it may serve a narrow purpose, most domains expect at least a handful of tools for interactive tasks.
The tools only provide static lists. Missing core actions like selecting a scenario, submitting scores, or user interactions make the surface incomplete for the implied game domain.