bjjgraph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BJJGRAPH_DATA | No | Path to an existing BJJGraph checkout folder (or to a bundle file) to use instead of the downloaded data/bjjgraph.json |
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 |
|---|---|
| bjj_searchA | Fuzzy search positions, transitions (sweeps, passes, escapes, takedowns…), submissions, systems, principles and learning notes by name or alias. Partial English names work; common Korean terms are translated. |
| bjj_get_techniqueA | Full detail for one transition or submission: outcomes and probabilities, conditions, key principles, setup, execution steps, common counters, common errors, training progressions, defender recognition cues / defensive options / escapes, variants, related content, safety and video clips. Use |
| bjj_get_positionB | Detail for one position, for the top and/or bottom role: overview, state properties and metrics, key principles, decision tree, common errors, drills, the technique menu with attempt weights, related positions and clips. |
| bjj_position_optionsA | Lists the transitions and submissions that can be attempted from a position in a given role, most commonly attempted first, with success rate and where each outcome (success / failure / counter) leads. |
| bjj_find_pathsA | Finds a few shortest routes from one position to another using only successful technique outcomes (e.g. Half Guard bottom → Back Control top). Each step lists the techniques that achieve it. The target may also be a submission (e.g. "Armbar"): routes then end at a position where it can be attempted. |
| bjj_listA | Lists entries of one kind with a one-line summary: systems (game plans / courses), principles, learning notes, positions or submission families. Optional text filter. |
| bjj_get_conceptA | Full content of a system (game plan, with study guide and sources), a principle (component skills, decision framework, errors, training approaches) or a learning note. |
| bjj_aboutB | Which BJJGraph version is loaded (commit, fetch date, counts), how to refresh it, and the data licence. |
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 8 tools
Each tool targets a fairly distinct resource+action: search (fuzzy across all), list (enumerate one kind), get_technique/get_position/get_concept (detail per entity type), position_options (menu for a role), find_paths (routing), about (metadata). The closest pair is bjj_list vs bjj_search and bjj_position_options vs bjj_get_position, but the descriptions make the boundaries clear enough that an agent should pick correctly.
All tools share the bjj_ prefix and snake_case, with a mostly predictable verb-first pattern (search, list, get_technique, get_position, get_concept, find_paths) plus two noun-ish outliers (position_options, about). Minor deviation but highly readable.
Eight tools is well-scoped for a read-only knowledge graph: retrieval by search, enumeration, per-entity detail, position menus, pathfinding, and metadata. No obvious redundancy or missing bulk operations that would warrant extra tools.
The surface covers discovery (search/list), drill-down (get_technique/get_position/get_concept), role-based options, and navigation (find_paths), plus version metadata. Minor gaps like no explicit reverse lookup (e.g. techniques that end in a position) or bulk compare are workaroundable via search and find_paths.