Commander Workshop 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cardsB | Search the verified local card catalog with bounded pagination. |
| load_collection_snapshotC | Normalize a supported local collection file into an immutable snapshot. |
| load_deckC | Normalize deck text without treating it as evidence of ownership. |
| search_libraryC | Search a stored collection without disclosing its contents in the summary. |
| check_deckC | Check exact construction legality without inferring bracket fit. |
| analyze_deckC | Store evidence-backed structural metrics without a scalar power score. |
| plan_deckC | Evaluate one to eight complete client-submitted candidates. |
| compare_decksB | Compare two to eight raw decks or plan winners without scalar scoring. |
| resolve_availabilityC | Resolve complete decks against physical copies without reserving them. |
| create_fulfillment_planB | Allocate each physical copy once inside an immutable plan result. |
| price_purchasesC | Price unresolved purchases without adding to a cart or buying anything. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| current_commander_rules | The locally pinned and verified Commander rules snapshot. |
| scenario_presets | Safe editable Commander planning scenario presets. |
TDQS
Scored across 11 tools
Each tool targets a distinct operation: searching card catalogs vs collections, loading different file types, checking legality vs analyzing metrics vs evaluating candidates, comparing, resolving availability, creating fulfillment plans, and pricing. No two tools appear to overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_cards, load_deck, check_deck). The verbs are varied but clear, and the nouns accurately describe the target resource. The pattern is uniform across all 11 tools.
With 11 tools, the server covers the essential workflows for a Commander deck workshop: searching, loading, checking, analyzing, planning, comparing, fulfillment, and pricing. The count feels well-scoped without being overwhelming or insufficient.
The tool set covers the full lifecycle from card and collection intake through deck validation, comparison, availability resolution, and fulfillment. There is no obvious missing operation; all necessary steps for the intended domain are present.