Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

by matthewdtowles
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

get_realized_gains

Get realized gains from Magic: The Gathering sell transactions using FIFO cost basis. Requires API key.

Instructions

Get the user's realized gains from SELL transactions using FIFO cost basis. Premium-gated. Requires IWMM_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/portfolio.ts:43-49 (handler)
    The getRealizedGainsTool object defines the 'get_realized_gains' tool. Its handler calls apiFetch to GET /api/v1/portfolio/realized-gains (authenticated). No input parameters required.
    export const getRealizedGainsTool = {
  name: "get_realized_gains",
  description:
    "Get the user's realized gains from SELL transactions using FIFO cost basis. Premium-gated. Requires IWMM_API_KEY.",
  inputSchema: z.object({}),
  handler: () => apiFetch({ path: "/api/v1/portfolio/realized-gains", authenticated: true }),
};
  • src/tools/portfolio.ts:46-47 (schema)
    Input schema is an empty object (z.object({})), meaning no inputs are accepted.
      "Get the user's realized gains from SELL transactions using FIFO cost basis. Premium-gated. Requires IWMM_API_KEY.",
inputSchema: z.object({}),
  • src/tools/index.ts:75-75 (registration)
    The tool is registered in the tools array and is also accessible via the toolsByName lookup map.
    getRealizedGainsTool,

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations provided, so description alone must convey behavior. It specifies the operation (get realized gains), source (SELL transactions), and method (FIFO). Also notes access restrictions (premium, API key). Covers key behavioral traits.

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?

Extremely concise: one sentence and two brief fragments. Every word adds value, and the most critical information appears first.

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?

With no input schema and no output schema, the description covers the core purpose and prerequisites. Could mention return format or error cases, but current level is sufficient for a simple 0-parameter tool.

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?

Input schema has no parameters, so baseline is 4. Description adds value by explaining the computation context, which is unnecessary but not harmful.

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 realized gains from SELL transactions using FIFO cost basis. Distinguishes from sibling tools like get_cost_basis by specifying transaction type and method.

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 mentions 'Premium-gated' and 'Requires IWMM_API_KEY', providing prerequisites. Does not directly compare to alternatives like get_cost_basis, but context is sufficient.

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/matthewdtowles/iwantmymtg-mcp'

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