Skip to main content
Glama

Scryfall

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Cards

search_cards
Read-onlyIdempotent

Search Magic: The Gathering (MTG) cards using Scryfall's powerful query syntax (e.g. "c:red type:dragon", "set:neo rarity:mythic", "o:flying cmc<=3"). Returns matching MTG cards with names, types, oracle text, sets, rarities, and prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoSort order, e.g. 'name', 'released', 'usd', 'edhrec'.
queryYesScryfall search query, e.g. 'c:red type:dragon', 'set:neo rarity:mythic'. Uses Scryfall's full-text query syntax.
uniqueNoRollup mode (default 'cards').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "order": "usd",
+    "query": "c:red type:dragon"
+  },
+  {
+    "query": "set:neo rarity:mythic",
+    "unique": "prints"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. Description adds value by specifying return fields (names, types, oracle text, etc.) and using external syntax (Scryfall). No contradictions. Still lacks pagination details, but acceptable.

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 concise sentences, front-loaded with purpose, then examples. No unnecessary words, highly efficient.

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

Completeness5/5

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

Despite no output schema, description fully explains return values (names, types, oracle text, sets, rarities, prices). With examples and parameter guidance, it's complete for a search tool.

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 coverage is 100% so baseline 3. Description adds concrete examples for query, order, and unique, which help understanding beyond schema descriptions.

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?

Description explicitly states the tool searches MTG cards using Scryfall query syntax, with examples. It clearly distinguishes from siblings like get_card (single card) and list_sets (sets).

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?

Description gives clear query syntax examples and explains what is returned, but does not explicitly state when to use vs. alternatives like get_card or random_card. However, context from sibling names makes it fairly clear.

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

All Scryfall toolsInspect
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