MTG Bench

get_card

Read-only

Fetch full detail for ONE card by exact name or id: oracle text, mana cost, type line, format legalities, and a brief summary of its printings. Use get_card_printings instead when the complete printing list matters (choosing a specific art, set, or finish).

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"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`card`	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?

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context by enumerating the exact output fields (oracle text, mana cost, type line, format legalities, printings summary) and noting the 'exact name or id' constraint. This goes beyond the basic read-only hint.

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 with no filler. The first sentence front-loads the tool's purpose and result fields, and the second gives a conditional alternative. Every word earns its place.

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?

The description is adequate for a card-detail fetch: it states what data is returned and when to choose a different tool. The presence of an output schema means return structure doesn't need to be explained. It doesn't cover error behavior (e.g., not found), but given the tool's simplicity and annotations, it is sufficiently complete.

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?

With 0% schema description coverage, the description must compensate for the parameters. It clarifies that 'name' and 'id' are acceptable for exact-match lookup, but it completely omits the 'slug' parameter present in the schema. This leaves a gap for the agent's understanding of all available inputs.

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's action ('Fetch full detail for ONE card') and specifies the exact resources returned (oracle text, mana cost, type line, format legalities, and a brief summary of printings). It also distinguishes itself from the sibling tool get_card_printings by explicitly deferring printing-list use cases.

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 provides explicit guidance to use get_card_printings instead when a complete printing list matters, giving a clear exclusion and alternative. It implies usage for exact-name/id lookups but does not mention other sibling tools like search_cards for fuzzy lookups, so it is not fully exhaustive.

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?