iwantmymtg-mcp

get_portfolio_breakdown_cards

Read-only

Retrieve the individual cards for a specific slice of a portfolio breakdown, such as a set, rarity, type, color, or cost-basis bucket. Use this to drill down from aggregated portfolio data into detailed card listings.

Instructions

Get the cards inside one slice of a portfolio breakdown (the drill-down for get_portfolio_breakdown). Premium-gated. Requires IWMM_API_KEY.

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": {
      "by": "<by>",
      "key": "<key>"
    },
    "name": "get_portfolio_breakdown_cards"
  }
}

Input Schema

Name	Required	Description
`by`	Yes	Dimension the slice belongs to. Must match the get_portfolio_breakdown call.
`key`	Yes	Slice key from the breakdown: a set code, rarity, type, cost-basis bucket, or color code.
`colors`	No	Only for by=color: the same superset filter (W,U,B,R,G,C) passed to get_portfolio_breakdown, so the drill-down matches the aggregate row. Ignored for other dimensions.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.2Jul 9, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
Addedv0.6.0Jun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true; description adds premium-gated and requires IWMM_API_KEY, which is valuable authorization context. No contradiction.

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 conveying purpose, relationship to parent tool, and access requirements. No wasted words.

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?

Lacks output schema but description is sufficient for a read operation. Could mention pagination or response format, but not critical for understanding the tool's core function.

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 3 is appropriate. Description does not add additional meaning beyond what the schema provides for the three parameters.

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 retrieves cards inside one slice of a portfolio breakdown, distinguishing it from get_portfolio_breakdown. Uses specific verb 'Get' and resource 'cards inside one slice of a portfolio breakdown'. Different from siblings.

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?

Implicitly guides usage as a drill-down after get_portfolio_breakdown. Mentions premium-gating and API key requirement. Could explicitly state when not to use or alternatives, but context is clear enough.

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

Deploy Server