Skip to main content
Glama

export_rulings

Export OPTGC card rulings as a stable, versioned JSON envelope for downstream tools, defaulting to reviewed, non-superseded results and filterable by card, date, authority, or source.

Instructions

Export rulings in a stable, versioned JSON envelope (shared with optcg-ingest export-rulings) for downstream consumers such as optcg-engine. Defaults to reviewed, non-superseded rulings; filter optionally by card_id, since (YYYY-MM-DD), min_authority (authority <= N), and source ('official_faq'|'errata'|'judge'|'community').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_rulings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNo
sourceNo
card_idNo
min_authorityNo
include_supersededNo
include_unreviewedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the important behavioral facts: the output is a stable, versioned envelope, and the default result set excludes unreviewed and superseded rulings. It does not mention permissions/auth requirements, result-size limits, or pagination expectations for large exports.

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?

A single dense sentence that front-loads the operation and output contract, then enumerates filters; the format hint and enum list each earn their space by adding information absent from the schema.

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

Completeness5/5

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

An output schema exists so return-shape explanation is not required, yet the description still states the envelope contract; combined with the default filtering behavior and filter semantics, an agent has everything needed to call this export correctly without extra 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?

Schema description coverage is 0%, so the description must compensate, and it does for four of six parameters: 'since (YYYY-MM-DD)' adds the format, 'min_authority (authority <= N)' clarifies the comparison direction (the schema alone is ambiguous), and it supplies the source enum values ('official_faq'|'errata'|'judge'|'community') that the schema lacks. The include_superseded and include_unreviewed booleans are only implied by the stated defaults rather than explained.

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?

The description states a specific verb and resource ('Export rulings') and pins down the output contract ('stable, versioned JSON envelope (shared with `optcg-ingest export-rulings`)'), which makes it clearly distinct from per-card readers like get_card_rulings and from mutation siblings like add_ruling/mark_ruling.

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?

It names the intended consumer class ('downstream consumers such as optcg-engine') and declares the default scope (reviewed, non-superseded), so an agent knows when this bulk-export shape is appropriate. It stops short of explicitly naming when to prefer a sibling such as get_card_rulings for a single card lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.