MTG Tools — Commander deck review and mana bases

Build a Commander mana base

build_mana_base

Read-only

Generate 30–42 lands for a Commander within a USD purchase budget, optionally with acceleration. Supply ownedLands to buy only missing copies, lockedLands to keep specific lands, or currentLands with maxChanges for a limited upgrade. The USD budget minimum remains $20; it is a spending cap, not a target. Returns card quantities, reasoning, prices, coverage, warnings, and shopping links. Preview only: no saved build, email, purchase, or cart modification. Shopping imports match by card name; printing and final prices may differ. Always show warnings rather than describing a deficient build as optimal.

Input Schema

Name	Required	Description
`bracket`	No
`budgetUsd`	No
`landCount`	No
`maxChanges`	No	Maximum replaced land slots when currentLands is supplied.
`ownedLands`	No	Land copies already owned; budget and cart charge only missing quantities.
`lockedLands`	No	Required lands to retain, including quantities. Must be legal and not excluded.
`currentLands`	No	Existing mana base for a limited upgrade; these copies count as owned.
`commanderName`	Yes
`excludedCards`	No
`includeAcceleration`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 22, 2026

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"
+}

First observedOct 4, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond annotations (readOnly, non-destructive), it adds critical behavioral context: 'Preview only: no saved build, email, purchase, or cart modification'; 'USD budget minimum remains $20; it is a spending cap, not a target'; and 'Shopping imports match by card name; printing and final prices may differ.' It also instructs the agent to always show warnings rather than misrepresenting a deficient build.

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?

The description is front-loaded with the core purpose and every sentence carries actionable information—budget semantics, mode selection, preview-only scope, price caveat, and warning handling. It is dense but not bloated.

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

Completeness4/5

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

Given 10 parameters, no output schema, and preview-only behavior, the description covers the return contents ('card quantities, reasoning, prices, coverage, warnings, and shopping links') and the key behavioral risks. It does not elaborate on bracket or acceleration semantics, but the schema and annotations fill most remaining gaps.

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

Parameters3/5

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

Schema description coverage is only 40%, so the description must compensate. It usefully explains ownedLands, lockedLands, currentLands, and maxChanges, and clarifies budget cap semantics, but it leaves bracket, landCount, includeAcceleration, excludedCards, and commanderName mostly to bare schema types.

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?

The description states a precise verb and resource: 'Generate 30–42 lands for a Commander within a USD purchase budget, optionally with acceleration.' It clearly distinguishes the tool from siblings that change brackets, reduce cost, repair decks, search commanders, or upgrade precons.

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

Usage Guidelines4/5

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

It names three concrete usage modes: ownedLands to buy only missing copies, lockedLands to keep specific lands, and currentLands with maxChanges for a limited upgrade. It does not explicitly contrast with sibling tools, but the mode-based guidance is strong.

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

All MTG Tools — Commander deck review and mana bases tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?