Conqueror's Haki
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assert_conquerors_hakiA | Exert supreme willpower over a chaotic list of ideas/tasks/features. Knocks out the weak elements and forces a definitive, ranked priority list against one goal. Args: items_to_evaluate: Raw list of features, tasks, bugs, or ideas. north_star_goal: The one objective that matters now (e.g. "Launch MVP in 2 weeks", "Get 10 active users"). strictness_level: "Supreme King" → max 3 survivors; "Overwhelming" → exactly 1 survivor. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming is trivially consistent; the name follows a clear verb_noun pattern.
A single tool feels thin for a server, but it serves a focused purpose (prioritization), which is borderline acceptable.
The tool covers its single targeted operation well, but lacks any auxiliary or complementary operations, leaving notable gaps.