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

get_rulings

Retrieve official rulings for Magic: The Gathering cards using Scryfall UUIDs to clarify card interactions and resolve gameplay questions.

Instructions

Get official rulings for a card by Scryfall UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Handler function for get_rulings tool: fetches rulings via Scryfall helper and returns JSON-formatted response.
    async ({ id }: { id: string }): Promise<ToolResult> => {
        const data: unknown = await Scryfall.getRulingsById(id);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] } as any;
    }
  • Input schema for get_rulings: requires a UUID string for the card ID.
    const getRulingsParamsShape = { id: z.string().uuid() } as const;
  • Registration of the get_rulings tool with MCP server, including description, schema, and handler.
    server.registerTool(
        "get_rulings",
        {
            description: "Get official rulings for a card by Scryfall UUID.",
            inputSchema: getRulingsParamsShape
        },
        async ({ id }: { id: string }): Promise<ToolResult> => {
            const data: unknown = await Scryfall.getRulingsById(id);
            return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] } as any;
        }
    );
  • Helper method in Scryfall object that fetches rulings for a card ID via Scryfall API.
    getRulingsById: (id: string) => getJson(`/cards/${encodeURIComponent(id)}/rulings`)
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 states the action ('Get official rulings') but does not describe traits such as whether it's read-only, 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 core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action, resource, and method concisely.

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 (a read operation with one parameter), no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, or error handling. For a tool with minimal structured data, the description should provide more context to be fully helpful.

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 input schema has one parameter ('id') with 0% description coverage, and the description adds meaning by specifying it as a 'Scryfall UUID'. This clarifies the parameter's purpose beyond the schema's format hint. However, it does not provide additional details like examples or constraints, so it partially compensates for the low schema coverage.

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 tool's purpose: 'Get official rulings for a card by Scryfall UUID.' It specifies the verb ('Get'), resource ('official rulings for a card'), and method ('by Scryfall UUID'). However, it does not explicitly differentiate from sibling tools like 'get_card' or 'csb_card', which might retrieve card data rather than rulings.

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. It mentions the method ('by Scryfall UUID') but does not specify prerequisites, exclusions, or compare it to sibling tools like 'search_cards' or 'get_card' that might also relate to card information. Usage is implied but not explicitly defined.

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