Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

list_set_cards

Retrieve all cards from a Magic: The Gathering set with filters for rarity, type, format, and legality, paginated for easy browsing.

Instructions

List all cards in a set, paginated. Supports the same filters as search_cards (rarity, type, format, legality).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesSet code.
rarityNo
typeNo
formatNo
legalityNo
pageNo
limitNo

Implementation Reference

  • The main tool definition: name 'list_set_cards', input schema, and handler that calls apiFetch to GET /api/v1/sets/{code}/cards with optional filters.
    export const listSetCardsTool = {
      name: "list_set_cards",
      description:
        "List all cards in a set, paginated. Supports the same filters as search_cards (rarity, type, format, legality).",
      inputSchema: z.object({
        code: z.string().describe("Set code."),
        rarity: z.enum(["common", "uncommon", "rare", "mythic"]).optional(),
        type: z.string().optional(),
        format: z.string().optional(),
        legality: z.enum(["legal", "banned", "restricted"]).optional(),
        page: z.number().int().min(1).optional(),
        limit: z.number().int().min(1).max(100).optional(),
      }),
      handler: ({ code, ...rest }: { code: string } & Record<string, unknown>) =>
        apiFetch({
          path: `/api/v1/sets/${encodeURIComponent(code)}/cards`,
          query: rest as Record<string, string | number | undefined>,
        }),
  • Zod schema defining inputs: required 'code', optional filters (rarity, type, format, legality), and optional pagination (page, limit).
    inputSchema: z.object({
      code: z.string().describe("Set code."),
      rarity: z.enum(["common", "uncommon", "rare", "mythic"]).optional(),
      type: z.string().optional(),
      format: z.string().optional(),
      legality: z.enum(["legal", "banned", "restricted"]).optional(),
      page: z.number().int().min(1).optional(),
      limit: z.number().int().min(1).max(100).optional(),
    }),
  • Registration of listSetCardsTool in the tools array (line 56), making it available as a tool.
    export const tools: ToolDefinition[] = [
      // Read-only (no auth)
      searchCardsTool,
      getCardTool,
      getCardPricesTool,
      getCardPriceHistoryTool,
      searchSetsTool,
      getSetTool,
      listSetCardsTool,
      getSealedProductsTool,
      // Inventory (auth)
      listInventoryTool,
      getInventoryQuantitiesTool,
      addInventoryTool,
      updateInventoryTool,
      removeInventoryTool,
      // Transactions (auth)
      listTransactionsTool,
      recordTransactionTool,
      updateTransactionTool,
      deleteTransactionTool,
      getCostBasisTool,
      // Portfolio (auth; most are Premium-gated)
      getPortfolioSummaryTool,
      getPortfolioHistoryTool,
      getCardPerformanceTool,
      getCashFlowTool,
      getRealizedGainsTool,
      getPortfolioBreakdownTool,
      refreshPortfolioTool,
      // Price alerts (auth)
      listAlertsTool,
      createAlertTool,
      updateAlertTool,
      deleteAlertTool,
      // Notifications (auth)
      listNotificationsTool,
      getUnreadCountTool,
      markNotificationReadTool,
      markAllNotificationsReadTool,
    ];
  • Helper function apiFetch that builds the URL, adds query params, sets auth header if needed, and makes the HTTP request.
    export async function apiFetch<T = unknown>(req: ApiRequest): Promise<T> {
      const url = new URL(req.path, config.baseUrl);
      if (req.query) {
        for (const [k, v] of Object.entries(req.query)) {
          if (v !== undefined && v !== null && v !== "") {
            url.searchParams.set(k, String(v));
          }
        }
      }
    
      const headers: Record<string, string> = {
        Accept: "application/json",
        "User-Agent": "iwantmymtg-mcp/0.0.1",
      };
    
      if (req.authenticated) {
        const { requireApiKey } = await import("./config.js");
        headers["Authorization"] = `Bearer ${requireApiKey()}`;
      }
    
      if (req.body !== undefined) {
        headers["Content-Type"] = "application/json";
      }
    
      const res = await fetch(url, {
        method: req.method ?? "GET",
        headers,
        body: req.body !== undefined ? JSON.stringify(req.body) : undefined,
      });
    
      if (!res.ok) {
        const text = await res.text();
        throw new ApiError(res.status, text, {
          limit: res.headers.get("X-RateLimit-Limit") ?? undefined,
          remaining: res.headers.get("X-RateLimit-Remaining") ?? undefined,
          reset: res.headers.get("X-RateLimit-Reset") ?? undefined,
        });
      }
    
      if (res.status === 204) return undefined as T;
      return (await res.json()) as T;
    }
Behavior3/5

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

No annotations provided, so description bears full burden. Mentions pagination and filters but omits details on default page/limit, error handling, sorting, or output structure. Adequate but not thorough.

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 concise sentences with no redundant information. Purpose and key features 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?

Covers essential aspects (purpose, pagination, filters) but lacks output schema, default values, error handling, and ordering. Given 7 parameters and no annotations, description is minimally sufficient but leaves gaps.

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 only 14% (only 'code' described). Description adds meaning by grouping optional filters (rarity, type, format, legality) and mentioning pagination, but does not detail each parameter's exact behavior or accepted values for type/format.

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 verb 'List', resource 'cards in a set', and mentions pagination. References sibling tool search_cards for filter parity, differentiating it from other listing 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?

Description implies when to use this tool over search_cards (for a specific set vs. cross-set search), but does not explicitly state exclusions or when to use other siblings like get_card or list_inventory.

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