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

mtg-mcp-server

by Cladios34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

bulk_similar_cards

Read-onlyIdempotent

Identify Magic: The Gathering cards similar to a reference card using keyword, type, CMC, and text analysis. Filter results by format legality and price.

Instructions

Find cards similar to a given card.

Scores similarity based on shared keywords, type words, CMC proximity, and oracle text overlap. Optionally filter by format legality and price.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return
formatNoFormat filter (e.g. 'commander', 'modern'). Only returns legal cards.
card_nameYesName of the card to find similar cards for
max_priceNoMaximum USD price filter
response_formatNoOutput verbosity: 'detailed' (default) or 'concise'detailed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and open-world. The description adds behavioral context by detailing similarity factors (shared keywords, type words, CMC proximity, oracle text overlap), which goes beyond annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences are concise and front-loaded with purpose. The second sentence lists similarity factors efficiently. No wasted words, though it could benefit from a more structured format (e.g., bullet points).

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?

Given the tool has 5 parameters, no output schema, and moderate complexity, the description adequately covers the core functionality and filtering options. However, it lacks details on the output format (e.g., structure of results) and what 'limit' affects beyond schema description.

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?

Input schema has 100% coverage with descriptions for all 5 parameters. The description mentions filtering by format and price, but does not add significant new semantics beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Describes the tool as finding similar cards based on specific criteria (keywords, type words, CMC, oracle text). The purpose is clear and specific, but it does not explicitly differentiate from sibling tools like 'card_comparison' or 'build_around' that also deal with similarity.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. While it mentions optional filters, it does not indicate when not to use it or suggest other tools for different use cases (e.g., comparing two specific cards).

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