MTG Bench

get_card_printings

Read-only

List EVERY printing of a card (set, rarity, artist, finish, collector number). get_card already returns a short printings summary, so reach for this only when the full list is the point.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_card_printings"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No
`name`	No
`slug`	No

Output Schema

Name	Required	Description	Default
`printings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The readOnlyHint already signals safety, and the description adds behavioral context by emphasizing 'EVERY' printing and enumerating output fields (set, rarity, artist, finish, collector number). This goes beyond the annotation, though it does not mention potential response volume or ordering.

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-loaded with the primary action and followed by a brief alternative reference. Every clause earns its place, with no redundant or filler content.

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?

The tool is simple, has an output schema, and safe read-only annotations. The description explains what the tool does, when to use it, and what to expect, making it complete for this complexity level.

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

Parameters1/5

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

Schema description coverage is 0% for three optional parameters, and the description provides no guidance on how to select or prioritize id, name, or slug. The phrase 'of a card' is the only hint, which is insufficient for understanding parameter semantics.

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 uses a specific verb+resource: 'List EVERY printing of a card' with concrete fields in parentheses. It explicitly distinguishes itself from get_card, which returns a short summary, making the tool's unique purpose unmistakable.

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

Usage Guidelines5/5

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

It provides explicit when-to-use guidance: 'get_card already returns a short printings summary, so reach for this only when the full list is the point.' This names the alternative and sets a clear exclusion condition, which is exactly what this dimension asks for.

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

All MTG Bench 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?