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

CSB: Get card

csb_card

Fetch a Commander Spellbook card using its numeric ID to access specific card data from the Scryfall API for Magic: The Gathering.

Instructions

Fetch Commander Spellbook card by numeric ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Handler function that calls CSB.getCard(id) and wraps the result in structuredContent.
    async ({ id }: { id: number }) => {
        const res = await CSB.getCard(id);
        return { structuredContent: res } as any;
    }
  • Input schema defining a positive integer 'id' parameter.
    const csbCardInput = { id: z.number().int().positive() } as const;
  • Registers the 'csb_card' tool with MCP server, including schema and handler.
    server.registerTool(
        "csb_card",
        {
            title: "CSB: Get card",
            description: "Fetch Commander Spellbook card by numeric ID.",
            inputSchema: csbCardInput
        },
        async ({ id }: { id: number }) => {
            const res = await CSB.getCard(id);
            return { structuredContent: res } as any;
        }
    );
  • CSB.getCard utility that fetches card data from Commander Spellbook API endpoint /cards/{id} via getJson helper.
    getCard: (id: number) => getJson(`/cards/${id}`),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Fetch' but doesn't clarify if this is a read-only operation, requires authentication, has rate limits, or what the return format looks like. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 essential information without any wasted words. It directly states the tool's purpose, making it highly concise and well-structured for quick understanding.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns complex card data. It doesn't explain what 'card' entails (e.g., fields like name, text, rulings) or error handling, leaving the agent unprepared for effective use in a broader context.

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?

The description adds meaningful context beyond the input schema by specifying that the 'id' parameter is a 'numeric ID' for a 'Commander Spellbook card'. With 0% schema description coverage and only one parameter, this adequately compensates, though it could detail format constraints like ID ranges or examples.

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 action ('Fetch') and resource ('Commander Spellbook card by numeric ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_card' or 'csb_read_card_index', which likely serve similar purposes, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'get_card', 'search_cards', and 'csb_read_card_index', there's no indication of prerequisites, constraints, or comparative use cases, leaving the agent to guess based on tool names alone.

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