ASEKE Compass Engine MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_system_infoA | Get detailed information about a Panksepp primary emotional system including neural basis, behavioral signature, CE demand, IS vulnerability profile, and political bridge. |
| get_pattern_infoA | Get detailed information about a named behavioral pattern including substrate, recognition signals, blind spots, and leverage points. |
| analyze_behaviorA | Scaffold an ASEKE analysis of a behavior, situation, or conflict. Returns the 5-step framework scoped to the most plausible candidate patterns for THIS situation, plus the output discipline. Does not perform the analysis — the caller does, using this as the frame. |
| match_patternsA | Lexical prefilter over the pattern library. Given observed behavioural signals, returns the closest candidate patterns WITH their recognition text so the caller can judge fit. This is token overlap, not comprehension — treat results as a shortlist to verify, never as a verdict. |
| list_allA | List all available primary emotional systems and named behavioral patterns in the ASEKE framework. |
| bridge_to_politicalA | Given active primary emotional systems, assess probable political orientation tendencies via the Dual Process Model bridge (FEAR to RWA, CARE breadth to SDO, etc). Returns DPM tendencies with caveats about timescale and IS dependence. |
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 clearly distinct purpose: retrieving system info, retrieving pattern info, listing all entities, scaffolding analysis, matching patterns, and bridging to political orientation. Even get_pattern_info and match_patterns differ clearly (lookup by name vs. lexical search). No meaningful overlap exists.
Names follow a mostly consistent snake_case verb-first pattern (get, list, analyze, match, bridge). Minor deviations: 'list_all' omits a specific noun, and 'bridge_to_political' uses a prepositional phrase, but the overall style remains predictable and readable.
Six tools is well-scoped for a specialized framework engine. Each tool earns its place, and the count falls comfortably in the ideal 3-15 range, balancing coverage without bloat.
The tool set covers the full intended workflow: discovering resources (list_all), retrieving detailed info (get_system_info, get_pattern_info), applying the framework (analyze_behavior, match_patterns), and extending to adjacent domains (bridge_to_political). The deliberate separation of scaffolding from execution is a designed feature, not a gap.