Skip to main content
Glama

MTG Tools — Commander deck review and mana bases

Repair deck roles and consistency

repair_deck
Read-only

Repair deck roles and consistency for a Commander deck within a USD budget. Accepts a quantity-prefixed decklist or a supported public deck URL. Returns proposed swaps, role counts, warnings, estimated costs, and optional TCGplayer links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deck": "<deck>",
      "commander": "<commander>"
    },
    "name": "repair_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesFull quantity-prefixed decklist, or a public HTTPS Moxfield/Archidekt deck URL without query parameters.
ownedNoQuantity-prefixed owned cards, up to 150 card entries and 16000 characters. Split larger collections before analysis.
lockedNo
qaTestNoInternal QA only: set true when the user explicitly says this is our test run. Excludes the call from usage/revenue statistics. Omit for normal player requests.
bracketNo
excludedNo
budgetUsdNo
commanderYes
maxChangesNo
replaceCardNo
searchContextNoOptional opaque context from a preceding card search for attributing a related request.
collectionModeNocollection_only uses only available owned cards; collection_first prioritizes owned cards then purchases within budget. In collection modes, owned is total inventory including this deck; copies in this deck are reserved. One deck at a time, up to 150 entries. No safe swaps may be found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / searchContext / description
      Previous value: -"Return the opaque searchContext from the preceding card search when the user requests a follow-up. Never invent it or run follow-ups automatically."New value: +"Optional opaque context from a preceding card search for attributing a related request."
  2. Changed1 schema field changed
    • addedInput schema / properties / searchContext
      Added value: +{
      +  "description": "Return the opaque searchContext from the preceding card search when the user requests a follow-up. Never invent it or run follow-ups automatically.",
      +  "maxLength": 400,
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / collectionMode
      Added value: +{
      +  "description": "collection_only uses only available owned cards; collection_first prioritizes owned cards then purchases within budget. In collection modes, owned is total inventory including this deck; copies in this deck are reserved. One deck at a time, up to 150 entries. No safe swaps may be found.",
      +  "enum": [
      +    "standard",
      +    "collection_only",
      +    "collection_first"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / qaTest
      Added value: +{
      +  "const": true,
      +  "description": "Internal QA only: set true when the user explicitly says this is our test run. Excludes the call from usage/revenue statistics. Omit for normal player requests.",
      +  "type": "boolean"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / deck / description
      Added value: +"Full quantity-prefixed decklist, or a public HTTPS Moxfield/Archidekt deck URL without query parameters."
    • addedInput schema / properties / replaceCard
      Added value: +{
      +  "default": "",
      +  "maxLength": 150,
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / owned / description
      Added value: +"Quantity-prefixed owned cards, up to 150 card entries and 16000 characters. Split larger collections before analysis."
  7. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description usefully confirms it is advisory ('returns proposed swaps') rather than applying changes. However it does not disclose why idempotentHint is false (likely price volatility / external lookups) or any rate-limit or external-fetch caveats despite openWorldHint=true. The return-content summary is the main value added.

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?

Three sentences with the core purpose front-loaded, followed by accepted inputs and then outputs — a sensible order with no filler. Slightly compressed at the cost of param detail, but no sentence is wasted.

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

Completeness3/5

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

For a 12-parameter, mutation-free analysis tool with no output schema, the description does reasonably well by enumerating what comes back (swaps, role counts, warnings, costs, TCGplayer links). It nevertheless leaves the majority of parameters unexplained and omits behavior around external lookups and non-idempotency, so an agent cannot fully predict its call semantics from the definition alone.

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

Parameters2/5

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

Schema description coverage is only 42% across 12 parameters, and the description compensates for almost none of it — the budget, decklist/URL, and 'maxChanges'-adjacent 'proposed swaps' are hinted at, but locked, excluded, replaceCard, bracket, maxChanges, and commander carry no meaning in the prose. It does not explain reserved owned copies or how collectionMode interacts with budget, both of which materially change results.

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

Purpose4/5

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

The description gives a specific verb and resource — 'Repair deck roles and consistency for a Commander deck' — plus a hard scoping constraint ('within a USD budget') and the accepted input forms (quantity-prefixed decklist or public deck URL). An agent can distinguish it from import_deck or delete_collection_plan, but it never explicitly contrasts itself with the nearest siblings such as find_replacements or reduce_deck_cost.

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

Usage Guidelines2/5

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

Usage context is implied (Commander deck, USD budget, decklist or URL input), but there is no explicit statement of when this tool is the right choice versus find_replacements, reduce_deck_cost, upgrade_precon, or change_deck_bracket. No prerequisites, exclusions, or alternative-selection guidance are provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources