Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

by matthewdtowles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_transactions

Read-only

Retrieve your MTG transaction history with pagination, sorting, and filtering. Free accounts access last 30 days; Premium users view full history.

Instructions

List the authenticated user's transactions, paginated. Supports sort/filter query params. Free tier sees the last 30 days only; Premium gets full history. Requires IWMM_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sortNoSort key (e.g. TX_DATE, TX_TYPE, TX_CARD, TX_PRICE).
typeNo
limitNo
ascendNoSort direction: true for ascending, false for descending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.7
    • addedInput schema / properties / ascend
      Added value: +{
+  "description": "Sort direction: true for ascending, false for descending.",
+  "type": "boolean"
+}
    • removedInput schema / properties / order
      Removed value: -{
-  "enum": [
-    "asc",
-    "desc"
-  ],
-  "type": "string"
-}
  2. Changed1 schema field changedv0.6.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  3. First observedv0.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark the tool as readOnlyHint:true, and the description confirms it lists data. Description adds value by specifying the auth requirement (IWMM_API_KEY) and tier-based data access limitation, which are not in 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?

Three short sentences, each adding distinct information: purpose, capabilities, and constraints. No wasted words; the key details are front-loaded.

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

Completeness3/5

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

Description covers purpose, pagination, sorting, filtering, auth, and tier restrictions. However, it lacks details on pagination behavior (e.g., default limit, cursor) and does not describe the response format, which is important given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40% (2 of 5 parameters have descriptions). The description only generically mentions 'sort/filter query params' without elaborating on specific parameters like page, type, or limit. It adds minimal value beyond the schema.

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?

Description clearly states 'List the authenticated user's transactions, paginated.' The verb 'List' and resource 'transactions' directly matches the tool name. Among siblings, it is distinct as there is no other transaction listing tool.

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?

Description mentions pagination, sort/filter support, and tier restrictions (Free vs Premium). It also notes the required API key. However, it does not explicitly state when not to use this tool or suggest alternatives, though the context makes it clear.

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