Skip to main content
Glama

tcgmcp

by com.tcgmcp

price_deck

Read-onlyIdempotent

Prices a pasted decklist (any TCG: Magic, Pokemon, Yu-Gi-Oh, One Piece, Lorcana, and 18+ more) and returns a ready-to-buy TCGplayer cart link. Paste the raw decklist text — one card per line, quantity + name, e.g. '4x Lightning Bolt' or '2 Counterspell (7ED)'. Returns a priced table (qty, name, set, unit price, line total), a grand total, any lines that couldn't be resolved with did-you-mean suggestions, and one affiliate-wrapped buy link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deckYesThe raw decklist text, one card per line (e.g. "4x Lightning Bolt\n2 Counterspell (7ED)").
gameNoOptional game hint (e.g. 'Magic', 'Pokemon', 'Yu-Gi-Oh', 'One Piece', 'Lorcana') when the decklist is ambiguous.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations (readOnlyHint, idempotentHint, destructiveHint) are consistent. Description adds rich behavioral details: returns priced table, grand total, unresolved lines with suggestions, and affiliate link. No contradictions.

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: first states purpose and supported TCGs, second gives format and output summary. No fluff, front-loaded, 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?

With full schema coverage, annotations, and no output schema needed (output described), description provides all necessary context. Siblings listed, usage clear.

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 covers both params with descriptions (100% coverage). Description adds example format and clarifies optional game hint for ambiguity, adding value beyond schema.

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 prices a decklist for multiple TCGs and returns a TCGplayer cart link. It distinguishes from siblings (list_printings, price_card) by focusing on full decklists.

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 explains when to use with paste of raw decklist, gives format example, and mentions optional game hint. Does not explicitly say when not to use, but context with siblings implies it's for full lists.

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

All tcgmcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: single-card price lookup, comparing printings, market trends, and deck pricing. The descriptions explicitly cross-reference each other to prevent confusion, such as list_printings noting when to use it instead of price_card.

Naming Consistency4/5

All tool names are lowercase with underscores, and most follow a verb_noun pattern (list_printings, price_card, price_deck). market_index is a slight deviation as a noun_noun phrase, but the naming remains intuitive and predictable.

Tool Count5/5

With only 4 tools, the server is tightly scoped to its purpose of TCG pricing and market data. Each tool covers a distinct need without redundancy, and the count is well within the ideal range for a focused server.

Completeness5/5

The tool surface covers the core workflows for TCG pricing: single card lookups, comparing printings, decklist pricing, and market trend analysis. There are no obvious missing operations for the stated domain, making the set feel complete.

Resources