optcg-knowledge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --db | Yes | Path to the local SQLite database file containing ingested rules, cards, FAQs, and rulings (e.g., /absolute/path/to/optcg-knowledge/data/optcg.db). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
One Piece Card Game (OPTCG) knowledge base exposing Comprehensive Rules, canonical cards, official FAQs/errata, and judge rulings with hybrid search. Authority hierarchy: 1=rules > 2=official_faq/errata > 3=judge > 4=community.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Hybrid search across OPTCG Comprehensive Rules, cards, FAQs, and judge rulings using exact-match OPTCG token detection (card IDs, rule numbers, [Keywords]), FTS5 BM25, and local sqlite-vec embeddings fused with RRF and authority tie-breaking. min_authority filters authority <= N (1=rules only, 2=rules+official_faq/errata, 3=+judge, 4=all). Superseded rulings are excluded unless include_superseded=True. |
| get_ruleA | Retrieve a specific OPTCG Comprehensive Rule by canonical rule_id (e.g. '7-1-4' or '7-1-4-1'), including its ancestor chain and, when include_children=True, all descendant sub-rules ordered numerically. |
| get_cardA | Look up an OPTCG card by canonical card_id (e.g. 'OP05-119', 'ST10-001', 'P-001') or by name (exact or fuzzy, ignoring punctuation differences like 'Monkey D Luffy'). Returns all matching canonical card printings/versions. |
| search_cardsA | Filter canonical OPTCG cards by name substring, color, exact cost, trait substring, effect/trigger keyword (e.g. '[Blocker]' or 'Rush'), and set_code (e.g. 'OP05'). Defaults to returning up to 25 matches (max 100). |
| get_card_rulingsA | Retrieve official FAQs, errata, and judge rulings linked to a canonical card_id (e.g. 'OP05-119'), ordered by authority ASC (1 highest .. 4 lowest), judge_tier (tier_0 > tier_2 > tier_1), then date DESC. Excludes superseded rulings by default unless include_superseded=True. |
| add_rulingB | Add a curated OPTCG ruling (always enters with reviewed=False) and index its chunk immediately in FTS5. Authority is derived from source ('official_faq'/'errata'=2, 'judge'=3, 'community'=4). Optional judge_tier ('tier_0' | 'tier_2' | 'tier_1', precedence tier_0 > tier_2 > tier_1) is valid for source='judge'. Never pass personal names, @handles, or Discord user IDs. |
| mark_rulingA | Update a ruling's reviewed status, link it as superseded_by a newer ruling_id, and/or set judge_tier ('tier_0' | 'tier_2' | 'tier_1' for source='judge'). Never deletes outdated rulings; rejects self-superseding and circular chains. |
| list_unreviewed_rulingsA | List curated rulings pending human review (reviewed=False), ordered by authority, judge_tier (tier_0 > tier_2 > tier_1), and date DESC (default limit=20, max 100). |
| export_rulingsA | Export rulings in a stable, versioned JSON envelope (shared with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| juiz | OPTCG rules judge workflow: consult rules/cards/rulings, follow authority hierarchy (1=rules > 2=official_faq/errata > 3=judge [tier_0 > tier_2 > tier_1] > 4=community), cite exact IDs, surface conflicts and outdated rulings. |
| curar | Judge chat curation workflow: read a raw export under data/raw/judge_chats/, extract Q&A pairs, respect judge tiers (tier_0 > tier_2 > tier_1), strip personal identifiers, verify card/rule links, and call add_ruling. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or workflow: rule lookup, card lookup, card-specific rulings, hybrid search, structured card filtering, and ruling curation/export. The broad `search` tool is clearly positioned as a hybrid fallback, while `search_cards`, `get_card`, and `get_card_rulings` have specific structured purposes.
Most tools follow a predictable snake_case verb_noun pattern (`get_rule`, `add_ruling`, `export_rulings`). Minor deviations include the bare `search` and mixed noun ordering between `get_card_rulings` and `search_cards`, but the set remains readable and consistent overall.
Nine tools is well-scoped for a rules/card/ruling knowledge base, with retrieval, search, curation, review, and export all earning their place. There is no obvious bloat or thin coverage.
The surface covers core read paths for rules, cards, and rulings, plus a complete ruling curation lifecycle including review, supersession, and export. Minor gaps remain, such as no direct `get_ruling` by ruling_id and no explicit bulk rule/card listing beyond search/filter tools.