Skip to main content
Glama
Sign In
mtg-mcp-server

mtg-mcp-server

by Cladios34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

scryfall_card_rulings

Read-onlyIdempotent

Retrieve official rulings and clarifications for any Magic: The Gathering card by providing its exact name.

Instructions

Get official rulings and clarifications for a Magic card.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCard name to get official rulings for (exact match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, which the description does not contradict. The description adds the context of 'official' rulings, which is useful. No additional behavioral traits are disclosed beyond what annotations provide.

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?

A single sentence containing only essential information. No fluff or redundancy. Front-loaded with the action and object.

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?

The description is minimal and adequate for a simple lookup tool with one parameter. However, since there is no output schema, the user might benefit from knowing the type of data returned (e.g., list of rulings). This is a minor gap.

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 100% and the parameter description in the schema ('Card name to get official rulings for (exact match)') is already precise. The tool description adds no extra meaning beyond the schema, meeting the baseline.

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 clearly states the tool gets official rulings for a Magic card. It uses a specific verb ('Get') and resource ('official rulings and clarifications'), and among sibling tools, it is distinct from card search or details tools.

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?

The description implies the tool is for ruling lookups, but does not explicitly state when to use it over alternatives like scryfall_card_details or other search tools. The context is clear but lacks explicit exclusions.

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

Deploy Server

Other Tools