Skip to main content
Glama
Cladios34

mtg-mcp-server

by Cladios34

hand_probability

Read-onlyIdempotent

Calculate the exact hypergeometric probability of drawing a specific card category by a given turn. Supports decklist validation to prevent miscounts.

Instructions

Compute the exact hypergeometric probability of seeing a card category.

Answers questions like "what are the odds I've seen at least 1 of my 3 tutors by turn 4?" via the closed-form hypergeometric distribution.

Pass decklist + category_filter to have the count MEASURED rather than stated. A probability computed from a number nobody re-checked is the failure this guards against: a category declared at 13 that had quietly become 11 moved the headline statistic by 6.5 points, unnoticed across every revision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
copiesNoNumber of matching cards in the deck
decklistNoThe actual decklist. Supplied with category_filter, 'copies' is counted from it instead of trusted, and any disagreement is reported as drift.
deck_sizeNoTotal cards in the library (default 99 for Commander)
max_countNoMaximum matching cards to count as a hit (inclusive, default: no cap)
min_countNoMinimum matching cards to count as a hit (inclusive)
cards_seenNoCards drawn/seen so far (default 7 for an opening hand)
category_filterNoFilter defining the category to count in decklist, e.g. 'mv<=1 t:creature'. Supports mv/cmc comparisons, t:, o:, name:, kw:.
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, ensuring safety. The description adds behavioral context: it uses closed-form hypergeometric distribution, performs drift detection when decklist+category_filter is provided, and warns about the risk of uncounted copies. No contradiction with annotations.

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

Conciseness3/5

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

The description is front-loaded with purpose and includes an engaging example, but the cautionary story adds length without essential information. It could be more concise without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite covering parameters and usage, the description fails to specify the return format or structure. With no output schema, agents lack critical information about what the tool returns (e.g., probability value, drift details), making it incomplete.

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 coverage is 100% with descriptions for all 7 parameters, so baseline is 3. The description adds value by explaining the interaction between decklist and category_filter for measured counts, and the drift concept, which is not captured in individual parameter descriptions.

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 computes exact hypergeometric probability for card categories, with a specific example. This distinguishes it from sibling tools like simulate_opening_hands, which use simulation, and other deck analysis tools.

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 how to use the tool for probability queries and highlights the drift-checking feature when providing a decklist and category_filter. It does not explicitly exclude alternatives, but the context is sufficient for typical usage.

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/Cladios34/mtg-mcp-server'

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