Skip to main content
Glama

MTG Tools — Commander deck review and mana bases

Find lower-cost deck replacements

reduce_deck_cost
Read-only

Find lower-cost deck replacements 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": "reduce_deck_cost"
  }
}

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.4/5.0
Behavior4/5

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

The annotations already establish that this is a non-destructive, read-only, open-world operation. The description adds useful behavioral context by stating that it returns proposed swaps, role counts, warnings, estimated costs, and optional TCGplayer links. It does not discuss limits on swap quality or external lookup behavior, but it goes meaningfully beyond the annotations.

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

Conciseness5/5

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

The description is three tight sentences with the main action and scope front-loaded. Every sentence adds useful information about inputs or outputs, with no wasted wording.

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

Completeness2/5

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

This is a complex tool with 12 parameters, no output schema, and low schema description coverage. The description says what is returned at a high level, but it omits material details about collection modes, ownership constraints, exclusions, and how cost estimates are produced.

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?

With 12 parameters and only 42% schema description coverage, the description needs to compensate but largely does not. It covers the deck input form and budget context, but leaves key parameters such as owned, collectionMode, locked, excluded, maxChanges, replaceCard, and qaTest unexplained.

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 states a specific verb and resource: finding lower-cost deck replacements for a Commander deck within a USD budget. It also identifies accepted input formats, making the tool's purpose clear. It does not explicitly distinguish this from sibling tools such as find_replacements or upgrade_precon.

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

Usage Guidelines3/5

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

The description implies usage for budget-constrained Commander deck reduction and notes that it accepts a decklist or public deck URL. However, it gives no explicit when-to-use versus when-not-to-use guidance and does not name alternatives like find_replacements or upgrade_precon.

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