Skip to main content
Glama
latte-chan
by latte-chan

CSB: Find combos by card IDs

csb_find_combos_by_card_ids

Find Magic: The Gathering combos enabled by specific Commander Spellbook card IDs, including exact and partial matches.

Instructions

Find combos that the provided cards enable (exact and almost-included).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesCommander Spellbook numeric card IDs
limitNo
offsetNo

Implementation Reference

  • Inline handler function for the MCP tool 'csb_find_combos_by_card_ids' that delegates to CSB.findMyCombos and formats the response.
    async ({ ids, limit, offset }: { ids: number[]; limit?: number; offset?: number }) => {
        const res = await CSB.findMyCombos(ids, limit, offset);
        return { structuredContent: res } as any;
    }
  • Zod input schema defining parameters: ids (array of nonnegative integers), optional limit (1-100), optional offset (>=0).
    const csbFindCombosInput = {
        ids: z.array(z.number().int().nonnegative()).min(1).describe("Commander Spellbook numeric card IDs"),
        limit: z.number().int().min(1).max(100).optional(),
        offset: z.number().int().min(0).optional()
    } as const;
  • Registration of the MCP tool with name, metadata (title, description, inputSchema), and handler function.
    server.registerTool(
        "csb_find_combos_by_card_ids",
        {
            title: "CSB: Find combos by card IDs",
            description: "Find combos that the provided cards enable (exact and almost-included).",
            inputSchema: csbFindCombosInput
        },
        async ({ ids, limit, offset }: { ids: number[]; limit?: number; offset?: number }) => {
            const res = await CSB.findMyCombos(ids, limit, offset);
            return { structuredContent: res } as any;
        }
    );
  • CSB helper method that constructs the API request to the Commander Spellbook backend's /find-my-combos endpoint with card IDs, limit, and offset.
    findMyCombos: (ids: number[], limit?: number, offset?: number) =>
        getJson("/find-my-combos", { ids: ids.join(","), limit, offset }),
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this is a read-only operation, what the output format looks like, whether results are paginated, or any rate limits. The mention of 'exact and almost-included' combos adds some behavioral context but is insufficient for a mutation-free tool.

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?

Single sentence with zero waste, front-loaded with the core purpose. Every word earns its place by specifying the action, resource, and key behavioral detail ('exact and almost-included').

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

Completeness2/5

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

For a 3-parameter tool with no annotations and no output schema, the description is incomplete. It doesn't explain the return format, pagination behavior (implied by limit/offset but not stated), or how 'almost-included' combos are determined. The context signals indicate significant gaps in documentation.

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 description coverage is only 33% (only 'ids' parameter has a description), but the description doesn't compensate by explaining 'limit' or 'offset' parameters. It implies 'ids' are 'Commander Spellbook numeric card IDs' but this is already in the schema. With low coverage and no additional parameter explanation, this meets the baseline for minimal compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Find' and resource 'combos' with the scope 'that the provided cards enable', specifying both 'exact and almost-included' combos. It distinguishes from sibling 'csb_find_combos_by_names' by using card IDs instead of names, but doesn't explicitly differentiate from other combo-finding tools like 'csb_variants_search'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'csb_find_combos_by_names' or 'csb_variants_search'. The description implies usage with numeric card IDs but doesn't specify prerequisites (e.g., needing Commander Spellbook IDs) or exclusions.

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/latte-chan/scryfall-connector'

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