Skip to main content
Glama

MTG Tools — Commander deck review and mana bases

Import a public Commander deck URL

import_deck
Read-only

Import a public HTTPS Commander deck URL as deck text, card count, and warnings. Archidekt Deck API: https://archidekt.com/forum/thread/16962481. Moxfield API access (private): https://moxfield.com/help/help-articles/faq#moxfield-api.

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": {
      "url": "<url>"
    },
    "name": "import_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
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.
searchContextNoOptional opaque context from a preceding card search for attributing a related request.

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. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered; the description adds real value by disclosing the output shape and the external provider dependencies (Archidekt Deck API, private Moxfield API). It does not explain the non-idempotent hint or failure behavior for private/invalid URLs, keeping it out of the 5 band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences front-load the purpose and output, and the API reference links are compact supporting evidence rather than filler. Nothing is repeated from the schema or annotations.

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?

With no output schema, the description correctly compensates by stating the three returned values, and it flags the external API dependency. What remains missing is whether importing persists a deck or merely parses text, and what happens on private or unsupported URLs.

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 coverage is 67%, and the two documented parameters (qaTest, searchContext) are already well described in the schema. The description does contribute meaning to the undocumented 'url' parameter by constraining it to a public HTTPS Commander deck URL, but it never enumerates supported hosts or URL format expectations.

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?

States a specific verb and resource ('Import a public HTTPS Commander deck URL') and names the return payload ('deck text, card count, and warnings'), which clearly separates it from the deck-mutation siblings like build_mana_base or repair_deck. It stops short of naming an explicit alternative, so it lands just below the top band.

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: the agent can infer this is for when a user supplies a public deck link, and the two API links hint at Archidekt/Moxfield as the supported sources. There is no explicit when-not guidance (private decks, unsupported sites) and no routing to a sibling such as save_collection_plan for persisting the result.

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