Manamancer's Agent is an OpenAI-powered assistant for Commander decks only. It can discuss the current list, search for candidates, and propose additions, cuts, or swaps. It cannot directly rewrite a deck. Concrete changes pass through Manamancer's own tools and server-side validator before the player sees an Apply or Dismiss action.
Last reviewed: August 2, 2026.
Why “validated” is a specific claim
A language model can produce fluent text without knowing whether a card name is real, whether that card is legal today, or whether its color identity fits the current commander. Manamancer does not use fluency as proof.
The validation claim applies to actionable recommendation chips produced through the Agent's proposal flow. For a proposed addition to reach that interface, the server checks it against the card index and Commander constraints. This is a narrower and more useful claim than saying “AI cannot make mistakes.” Generated prose can still contain a mistaken rules explanation, weak strategy, an outdated assumption, or a card mention that was not submitted as a proposed change.
The request starts with the actual deck
When a player starts an Agent run, Manamancer prepares a structured snapshot of the Commander deck and relevant conversation context. That snapshot includes the command zone, deck cards, staging-zone context, selected preferences, and the same core statistics used by the deck panel: card and land totals, average mana value, curve, colored symbols, and heuristic ramp, draw, removal, and wipe counts.
The model is instructed to treat deck content as untrusted data rather than as instructions. This matters for imported primers, card text, deck names, or other user-authored material that could otherwise look like a command when placed inside a prompt.
Manamancer's Privacy Policy explains the AI-related information flow and provider retention choices. The Agent is available on every signed-in account and shares that account's metered AI budget with the other covered AI routes; the plan sets the size of that budget, not whether the Agent can be used.
Tool 1: search the local card index
The model's card-discovery tool is search_cards, backed by Manamancer's local Scryfall-derived index and search compiler. It returns structured card records rather than asking the model to recall the entire Magic catalog from training.
For addition and swap modes, the server constrains searches to cards that are Commander-legal and within the current commander's color identity before executing them. The final validator repeats the important checks, so a search-filter problem does not become permission to surface a bad proposal.
Search results are limited, ranked responses to a query. They are not proof that the strategically best card was found, and the index can lag a new release or ban change until its next refresh. Search is the grounding source for recommendations, not a promise of exhaustive discovery.
Tool 2: register a proposed change
The second tool, propose_changes, records concrete additions and cuts. A card recommended as a deck change is supposed to go through this tool rather than exist only as persuasive prose. The resulting structured proposal is what Manamancer can validate and display as a chip.
The selected mode narrows what may survive:
- Ask is analysis-only; deck changes are rejected for that turn.
- Add accepts additions and prevents an attached replacement field from silently creating a cut.
- Cut accepts cuts rather than additions.
- Swap requires an addition to name the exact deck card it replaces, and validates the two sides as a pair.
These mode checks run on the server. They do not depend solely on whether the model followed the wording in its prompt.
The server-side addition checks
For every proposed addition, the validator applies deterministic checks before producing an actionable suggestion:
- Grounding: the card name must have appeared in a
search_cardsresult during that same server-side request. - Existence: the name must resolve to a real card in Manamancer's local card index.
- Commander legality: the indexed Commander legality must be
legal. - Color identity: once a commander or partner is selected, the card's identity must be a subset of the combined deck identity.
- Singleton state: a nonbasic card already in the deck is rejected as a duplicate.
- Pending and dismissed memory: a nonbasic card already waiting in the tray, or one the player explicitly dismissed, is not immediately proposed again.
- Collection-only mode: when enabled, the card must also appear in the player's owned-card names.
Nonbasic additions are clamped to one copy. Basic lands may use a larger quantity for a mana-base fill, with a conservative ceiling. The displayed suggestion uses the canonical name and structured details returned by the local card record.
If any check fails, that item is dropped rather than being converted into a chip. Dropped proposals can be grouped by reason and supplied back to the running Agent so it has a chance to choose a valid alternative within the bounded run.
Cuts and swaps have their own safeguards
A cut must match a card actually present in the deck. The Agent cannot cut the commander, partner, or companion. It also avoids duplicating a cut already waiting in the pending tray and respects a player's explicit decision to keep a previously dismissed cut.
A swap is meant to be one-for-one. The incoming card must pass all addition checks, and the named outgoing card must pass the cut checks. Two additions cannot both claim the same outgoing card in one run. If the cut side of a strict Swap-mode proposal fails, the whole swap is rejected instead of leaving behind an unrequested standalone addition.
Those rules protect deck state, but they do not prove that a swap preserves every strategic function. Replacing a removal spell with a legal creature may be structurally valid and strategically poor. The reasoning and the actual cards still deserve review.
Apply and Dismiss keep the player in control
The model receives search and proposal tools, not a general deck-mutation tool. A validated recommendation appears in the interface with a separate player decision:
- Apply performs the chosen addition, cut, or linked swap through the normal deck state flow.
- Dismiss records that decision and removes the pending recommendation without changing the list.
This separation is intentional. Validation determines whether a proposal is eligible to offer; the player determines whether it belongs in this deck. A recommended card can be real, Commander-legal, on-color, and still conflict with a budget, local playgroup, favorite theme, accessibility need, or desired power level.
What the safety boundary guarantees
For concrete additions that reach an Agent recommendation chip, the local validator is designed to prevent:
- a card invented by the model;
- a card the model never found through this run's search tool;
- a card absent from the local card index;
- a card indexed as not legal in Commander;
- an off-color addition after a command-zone identity exists;
- an ordinary singleton duplicate; and
- an unowned addition when collection-only mode is active.
It also verifies that cuts and swap targets exist in the editable deck and are not protected command-zone cards.
What it does not guarantee
The boundary does not make the Agent an official Magic rules authority. In particular, it does not guarantee:
- that every statement in the prose is correct;
- that a recommendation is optimal for a metagame or playgroup;
- that the imported card and ban data already reflect an announcement made after the latest index refresh;
- that the price shown will be available from a seller;
- that a legal combo works the way the prose describes; or
- that the resulting full deck is complete and legal after unrelated pending edits.
Use card detail and the format-legality view to inspect the finished list. Consult current Oracle text and official rules for difficult interactions. For Commander power expectations, talk with the table: a deterministic color check cannot replace Rule Zero.
A good review workflow
- Finish loading the deck and confirm the correct commander, partner, and companion.
- Choose Ask, Add, Cut, or Swap according to the change you actually want.
- State the deck's plan, budget, power target, and cards you want to keep.
- Use collection-only mode if ownership is a hard constraint.
- Read both the reasoning and the structured card details.
- Apply only the proposals you agree with, then recheck deck totals, statistics, and legality.
- Report a recommendation that appears to bypass the boundary with the deck URL, card name, mode, and a screenshot through the contact page.
The Agent is intentionally unavailable for advice on the other thirteen supported formats. Manamancer's ordinary search, builder, statistics, and format engine remain available for those decks without presenting a Commander validator as a universal AI safety check.
