Skip to main content
Glama

MTG Tools — Commander deck review and mana bases

Review a Commander bracket transition

change_deck_bracket
Read-only

Review a Commander bracket transition 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": "change_deck_bracket"
  }
}

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful context by enumerating the return payload (proposed swaps, role counts, warnings, estimated costs, TCGplayer links) and the budget constraint, but says nothing about failure modes, rate limits, or what happens when no 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. The output enumeration is dense but earns its place given there is no output schema.

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 and low schema coverage, the description covers purpose and return shape but leaves most parameter semantics and all usage routing unaddressed. It is adequate to identify the tool but not to invoke it confidently without reading the schema.

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 does not. It mentions only the deck input form and the USD budget, leaving bracket, maxChanges, replaceCard, collectionMode, owned, locked, and excluded entirely unexplained outside the schema.

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 ('Review a Commander bracket transition for a Commander deck') and adds the budget scoping constraint. It is clearly distinct from cost-reduction or precon-upgrade siblings, though it never names an alternative to route against.

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 by the phrase 'bracket transition' and the accepted input forms (decklist or public URL). There is no explicit when-to-use versus when-not, and no mention of prerequisites such as needing a target bracket or a budget before calling.

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