Skip to main content
Glama
Cladios34

mtg-mcp-server

by Cladios34

deck_mechanic_map

Read-onlyIdempotent

Map shared deck mechanics: keyword carrier counts, cost reductions, tribal types (including changelings), and trigger frequencies. Understand deck functionality beyond per-card data.

Instructions

Map the mechanics a deck SHARES — keyword carriers, tribal counts, trigger reach.

Every other tool here is indexed by card. This one is indexed by mechanic, and answers what per-card data cannot:

  • how many cards carry the commander's keyword (a deck with 15 carriers is not a loop toward one card, it is 15 destinations);

  • what a cost reducer ACTUALLY reduces, counted rather than assumed (rule 601.2f: a generic reduction never touches coloured pips);

  • who really has the tribal type, including changelings — every creature type by rule 702.73a, and invisible to a type-line search;

  • which triggers multiply per attacking creature versus firing once per combat.

Run this before writing any description of how a deck works.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
decklistYesCard names in the deck
commanderYesThe commander — its keywords seed the mechanic detection
response_formatNoOutput verbosity: 'detailed' (default) or 'concise'detailed
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint, openWorldHint, idempotentHint. The description adds valuable context about indexing by mechanic and answers per-card data cannot, including references to rules (601.2f, 702.73a). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured, front-loaded with core operation. Each sentence adds value, though it is somewhat lengthy. Could be slightly more concise but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the tool and absence of output schema, the description covers key aspects: keyword carriers, tribal counts, trigger reach, and explains why it's needed. Minor gap on output format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% so baseline is 3. The description adds context that the commander seeds mechanic detection and implies decklist is a list of card names. This enhances parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'Map the mechanics a deck SHARES' with specific verbs and resources. It distinguishes from siblings by explicitly stating 'Every other tool here is indexed by card. This one is indexed by mechanic.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells when to use this tool vs alternatives: 'Run this before writing any description of how a deck works.' It also lists specific scenarios like keyword carriers, cost reducer analysis, and trigger reach.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cladios34/mtg-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server