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

CSB: Search variants

csb_variants_search

Search Commander Spellbook combos by filtering with card usage, outcome production, or combo group identifiers to find specific Magic: The Gathering gameplay variants.

Instructions

Search Commander Spellbook variants (combos) by filters like uses/produces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usesNoFilter variants that use this CSB card ID
producesNoFilter variants that produce this feature ID (e.g., Win the game = 2)
ofNoFilter variants that are of a specific combo ID group
limitNo
offsetNo

Implementation Reference

  • Registers the 'csb_variants_search' tool with McpServer, providing title, description, input schema, and the handler function that delegates to CSB.variants.
    server.registerTool(
        "csb_variants_search",
        {
            title: "CSB: Search variants",
            description: "Search Commander Spellbook variants (combos) by filters like uses/produces.",
            inputSchema: csbVariantsSearchInput
        },
        async ({ uses, produces, of, limit, offset }: { uses?: number; produces?: number; of?: number; limit?: number; offset?: number }) => {
            const res = await CSB.variants({ uses, produces, of, limit, offset });
            return { structuredContent: res } as any;
        }
    );
  • Zod input schema definition for the csb_variants_search tool parameters.
    const csbVariantsSearchInput = {
        uses: z.number().int().nonnegative().optional().describe("Filter variants that use this CSB card ID"),
        produces: z.number().int().nonnegative().optional().describe("Filter variants that produce this feature ID (e.g., Win the game = 2)"),
        of: z.number().int().nonnegative().optional().describe("Filter variants that are of a specific combo ID group"),
        limit: z.number().int().min(1).max(100).optional(),
        offset: z.number().int().min(0).optional()
    } as const;
  • The inline handler function for the tool, which calls CSB.variants with the input parameters and returns structured content.
    async ({ uses, produces, of, limit, offset }: { uses?: number; produces?: number; of?: number; limit?: number; offset?: number }) => {
        const res = await CSB.variants({ uses, produces, of, limit, offset });
        return { structuredContent: res } as any;
    }
  • CSB.variants helper function that makes an HTTP GET request to the Commander Spellbook API /variants endpoint with query parameters.
    variants: (opts: { uses?: number; produces?: number; of?: number; limit?: number; offset?: number }) =>
        getJson("/variants", opts),
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 the search action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior (implied by limit/offset but not explained), or what the output looks like. For a search tool with 5 parameters and no annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Search Commander Spellbook variants (combos)') and includes key filtering information. There is zero wasted text, making it appropriately concise for a search tool.

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?

Given the complexity (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return format, pagination behavior (despite limit/offset parameters), error conditions, or how it differs from similar sibling tools. For a search operation with multiple filters and no structured output documentation, more context is needed.

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?

The description mentions 'filters like uses/produces', which adds context for two of the five parameters (uses, produces). With 60% schema description coverage, the schema documents all parameters but only three have descriptions (uses, produces, of). The description provides minimal additional meaning beyond the schema, compensating slightly but not fully for the coverage gap.

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 'Search' and resource 'Commander Spellbook variants (combos)', making the purpose understandable. It distinguishes from some siblings like 'csb_card' or 'get_card' by focusing on variants/combos rather than individual cards. However, it doesn't explicitly differentiate from 'csb_find_combos_by_card_ids' or 'csb_find_combos_by_names' which also search combos.

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?

The description mentions filtering by 'uses/produces', which implies usage for filtered searches, but provides no explicit guidance on when to use this tool versus alternatives like 'csb_find_combos_by_card_ids' or 'csb_find_combos_by_names'. There are no prerequisites, exclusions, or comparisons to sibling tools stated.

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