Skip to main content
Glama

MTG Tools — Commander deck review and mana bases

Build a Commander mana base

build_mana_base
Read-only

Generate a 30–42 land Commander mana base within a USD purchase budget of at least $20. Supports owned, locked, and excluded lands, limited upgrades, optional acceleration, and an optional TCGplayer cart.

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": {
      "commanderName": "<commanderName>"
    },
    "name": "build_mana_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
budgetUsdNo
landCountNo
maxChangesNoMaximum replaced land slots when currentLands is supplied.
ownedLandsNoLand copies already owned; budget and cart charge only missing quantities.
lockedLandsNoRequired lands to retain, including quantities. Must be legal and not excluded.
currentLandsNoExisting mana base for a limited upgrade; these copies count as owned.
commanderNameYes
excludedCardsNo
searchContextNoOptional opaque context from a preceding card search for attributing a related request.
includeAccelerationNo

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 / 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"
      +}
  4. Changed4 schema fields changed
    • addedInput schema / properties / currentLands
      Added value: +{
      +  "default": [],
      +  "description": "Existing mana base for a limited upgrade; these copies count as owned.",
      +  "items": {
      +    "properties": {
      +      "name": {
      +        "maxLength": 200,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "quantity": {
      +        "maximum": 99,
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "quantity"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 300,
      +  "type": "array"
      +}
    • addedInput schema / properties / lockedLands
      Added value: +{
      +  "default": [],
      +  "description": "Required lands to retain, including quantities. Must be legal and not excluded.",
      +  "items": {
      +    "properties": {
      +      "name": {
      +        "maxLength": 200,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "quantity": {
      +        "maximum": 99,
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "quantity"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 300,
      +  "type": "array"
      +}
    • addedInput schema / properties / maxChanges
      Added value: +{
      +  "default": 3,
      +  "description": "Maximum replaced land slots when currentLands is supplied.",
      +  "maximum": 10,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / ownedLands
      Added value: +{
      +  "default": [],
      +  "description": "Land copies already owned; budget and cart charge only missing quantities.",
      +  "items": {
      +    "properties": {
      +      "name": {
      +        "maxLength": 200,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "quantity": {
      +        "maximum": 99,
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "quantity"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 300,
      +  "type": "array"
      +}
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint=false, so safety and non-determinism are covered. The description usefully adds the hard constraints (land range, minimum budget) and discloses that an optional TCGplayer cart can be produced, which is external side-effect context beyond the annotations, but it doesn't explain how owned vs. locked vs. current lands interact for budget purposes.

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?

A single front-loaded sentence with a concrete verb-resource-range-money opening, followed by a compact list of supported options. Dense but each clause maps to a real feature; no filler.

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?

With 12 parameters, no output schema, and a cart-producing side effect, the description should say what the caller gets back and whether results persist (e.g., relation to save_collection_plan). It covers inputs and constraints well but leaves the output/return shape and a few parameters unexplained.

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 only 50%, and the description compensates by naming several optional behaviors: owned/locked/excluded lands, limited upgrades (mapping to currentLands/maxChanges), acceleration, and the TCGplayer cart. It still says nothing about bracket selection, qaTest, or searchContext, so the compensation is partial.

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?

States a specific verb and domain resource ('Generate a ... Commander mana base') plus concrete scope: 30–42 lands, USD budget floor of $20. This distinguishes it from siblings like upgrade_precon and repair_deck, which operate on existing decks rather than producing a mana base under a price constraint.

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 mention of 'limited upgrades' and 'supports owned, locked, and excluded lands' implies the situations the tool handles, but it never says when to pick this over upgrade_precon, repair_deck, or plan_collection. Guidance is implied rather than explicit.

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