quijutsu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP transport. Default is 3000. Only used with the HTTP transport. | |
| QUIJUTSU_SUPABASE_URL | No | URL of a QuiJutsu-compatible backend. Defaults to QuiJutsu's live project. | |
| QUIJUTSU_SUPABASE_ANON_KEY | No | Publishable (anon) key for the backend. Defaults to QuiJutsu's publishable key. | |
| QUIJUTSU_DEFAULT_TOURNAMENT_ID | No | Default tournament used when none is specified. Defaults to the World Anime Tournament. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_assetsA | Search the public QuiJutsu Community Asset Library: characters, abilities, locations, weapons and other named things from anime, each with its review status and community Spirit Level (1-8, how deep a fan needs to be to know it). Filter by name, type, anime title or Spirit Level. Returns one page plus total_count for paging. |
| get_asset_provenanceA | Explain the trust record behind one Community Asset Library entry. Returns origin (community = proposed by a player and confirmed by independent reviewers; imported = seeded by QuiJutsu), review_status, evidence_tier (how strong the cited source is), question_eligible (whether the game may build trivia on it), and the Spirit Level with its source, community score, the full public vote tally and whether it has crossed the certification threshold. Use this when a user asks whether an entry is reliable, who decided its difficulty, or why it is in the library. Look the asset up by name; pass asset_id to pick one when a name matches several. |
| list_anime_titlesA | List the anime titles that have public assets (with counts), the titles currently open for community contributions, and a breakdown of public assets by type and by Spirit Level. Call this first to learn which titles search_assets can filter on. |
| get_leaderboardA | Top QuiJutsu players. casual ranks by season points (monthly, annual or lifetime); ranked ranks by ELO rating, which ignores period. Returns usernames, scores and ranks only. |
| get_tournament_leaderboardA | Standings for a QuiJutsu tournament: rank, wins, losses, ELO, answer accuracy and average response time per player, plus total players, matches and a per-country player count. Defaults to the World Anime Tournament (25 Oct 2026). Filter by country to get a national leaderboard. |
| get_contributor_leaderboardA | Players who build the Community Asset Library, ranked by score. published = entries they proposed that went live, sourced = entries they found the citation for, reviews = reviews that matched how a submission settled. trust_level is their reviewer standing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct target: asset search vs. provenance lookup vs. title discovery vs. three separate leaderboard populations. The only mild overlap is between search_assets and list_anime_titles (both help discovery), but descriptions explicitly position list_anime_titles as a 'call this first' helper and search_assets as filterable paging, so misselection is unlikely. The three leaderboard tools are clearly differentiated by audience (players, tournament, contributors).
All six names follow a clean verb_noun snake_case pattern (search_assets, get_asset_provenance, list_anime_titles, get_leaderboard, get_tournament_leaderboard, get_contributor_leaderboard). The leaderboard family shares a predictable prefix/suffix structure, making relationships obvious.
Six tools is well-scoped for a read-only community-asset-and-leaderboard lookup server. Each tool covers a distinct query surface (assets, provenance, titles, three leaderboard types) with no filler.
The read-only lookup lifecycle is largely covered: discovery, search, provenance/trust, and leaderboards. Minor gaps exist — there is no direct get_asset-by-id tool (only search plus optional asset_id on provenance) and no tools for contributing or reviewing assets, which the descriptions imply is a core community workflow.