Skip to main content
Glama
j4th
by j4th

commander_comparison

Read-onlyIdempotent

Compare 2-5 Magic: The Gathering commanders head-to-head. See side-by-side stats including mana cost, color identity, EDHREC rank, combo count, and shared/unique staples.

Instructions

Compare 2-5 commanders head-to-head: stats, combos, staples, popularity.

Side-by-side comparison table with mana cost, color identity, EDHREC rank, combo count, and shared/unique staples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandersYes2-5 commander names to compare head-to-head
response_formatNoOutput verbosity: 'detailed' (default) or 'concise'detailed
Behavior4/5

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

Annotations already provide safety hints. Description adds specific output details (table with mana cost, color identity, etc.) beyond annotations.

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 the action and key details. No waste.

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?

Describes output format and content. Given annotations and simplicity, it is sufficiently complete. Could mention data freshness but openWorldHint covers that.

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?

Schema coverage is 100%, so baseline is 3. Description does not add meaning beyond what parameter descriptions already state.

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?

Clearly states the tool compares 2-5 commanders head-to-head, listing specific stats. Distinguishes from sibling tools like card_comparison and archetype_comparison.

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?

Explicitly indicates when to use (comparing commanders) but does not explicitly state when not to use or provide alternatives. However, the sibling list provides context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/j4th/mtg-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server