Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

by matthewdtowles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_portfolio_breakdown

Read-only

Break down your MTG collection value by set, rarity, type, color, or cost basis. See each slice's value, count, and share to identify where your collection's worth is concentrated.

Instructions

Get the user's collection value broken down by a dimension into slices (each with value, count, and share). Premium-gated. Use get_portfolio_breakdown_cards to drill into one slice. Requires IWMM_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byYesDimension to break down by. 'cost-basis' buckets are gain/loss/at-cost; 'color' groups by color identity.
colorsNoOnly for by=color: comma-separated identity codes (W,U,B,R,G,C; C is colorless) to keep only cards whose color identity contains all of them. Ignored for other dimensions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.9
  2. Removedv0.6.8
  3. Changed1 schema field changedv0.6.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  4. Changed3 schema fields changedv0.6.0
    • changedInput schema / properties / by / description
      Previous value: -"Dimension to break down by. 'cost-basis' buckets are gain/loss/at-cost."New value: +"Dimension to break down by. 'cost-basis' buckets are gain/loss/at-cost; 'color' groups by color identity."
    • changedInput schema / properties / by / enum
      Previous value: -[
-  "set",
-  "rarity",
-  "type",
-  "format",
-  "cost-basis"
-]New value: +[
+  "set",
+  "rarity",
+  "type",
+  "color",
+  "cost-basis"
+]
    • addedInput schema / properties / colors
      Added value: +{
+  "description": "Only for by=color: comma-separated identity codes (W,U,B,R,G,C; C is colorless) to keep only cards whose color identity contains all of them. Ignored for other dimensions.",
+  "type": "string"
+}
  5. First observedv0.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, so the description adds value by disclosing gating (Premium-gated) and authentication requirement (IWMM_API_KEY). It does not describe output format details beyond 'each with value, count, and share' or mention rate limits, data freshness, or side effects. This is adequate but not rich.

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?

The description is concise at two sentences, front-loading purpose and output format, then adding gating info and a sibling reference. Every sentence provides value with no fluff.

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?

Given the tool's complexity (enum with special cases, no output schema), the description covers core purpose, output structure partially, and references a key sibling. It omits details like overall summary alternative (get_portfolio_summary) but is sufficient for a read-only breakdown tool with well-documented parameters.

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% with descriptions for both parameters, including enum values and special behavior for 'cost-basis' and 'color'. The description does not add significant meaning beyond what the schema provides, so baseline 3 is appropriate.

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 function: 'Get the user's collection value broken down by a dimension into slices (each with value, count, and share).' It uses a specific verb ('Get') and resource ('collection value broken down'), and distinguishes from sibling 'get_portfolio_breakdown_cards' by noting it's for drilling into one slice.

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 usage context by noting it is 'Premium-gated' and 'Requires IWMM_API_KEY', and gives an explicit alternative: 'Use get_portfolio_breakdown_cards to drill into one slice.' However, it does not compare with other siblings like get_portfolio_summary or explicitly state when not to use this tool.

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