Skip to main content
Glama

MTG Tools — Commander deck review and mana bases

Upgrade a Commander precon

upgrade_precon
Read-only

Upgrade a Commander precon 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": "upgrade_precon"
  }
}

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by saying the output is *proposed* swaps (reinforcing that nothing is applied) along with role counts, warnings, costs and optional TCGplayer links, but it says nothing about limits, failure modes, or when no safe swaps exist.

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 tight sentences with the purpose front-loaded and no filler. Slightly efficient at the cost of coverage, but nothing is redundant with structured fields.

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 tool with no output schema, the description covers what comes back but leaves the majority of tuning parameters and their interactions (bracket, maxChanges, collectionMode, owned reservation) unexplained. The return-value sentence rescues it from being inadequate, but key behavioral knobs remain undocumented.

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, so the description must compensate and largely does not. It restates the deck input formats already documented in the schema and gestures at budgetUsd, but owned, locked, excluded, bracket, maxChanges, replaceCard and qaTest get no explanation of their effect on the upgrade.

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+resource ('Upgrade a Commander precon') plus scope qualifiers ('within a USD budget') and the accepted input forms (quantity-prefixed decklist or public deck URL). It is clearly distinguishable from siblings like import_deck or reduce_deck_cost, though it never explicitly names them.

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?

Usage is only implied: you infer you should call it when you want budget-constrained swap suggestions for an existing precon list. There is no explicit when-to-use vs. when-not guidance, no mention of find_replacements or plan_collection as alternatives, and no stated prerequisites.

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