Hegelion
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dialecticB | Dialectical reasoning (thesis → antithesis → synthesis). Modes: single_shot (one prompt), workflow (step-by-step recipe), thesis/antithesis/synthesis (individual phase prompts). Use response_style to control output: 'json', 'sections', or 'synthesis_only'. |
| autocodeB | Start autocoding (g3 coach-player paradigm). mode=init: create session state. mode=workflow: step-by-step recipe. mode=single_shot: one comprehensive prompt. |
| autocode_turnA | Execute one step in the autocoding loop. role=player: generate implementation prompt (advances state to coach). role=coach: generate verification prompt. role=advance: advance state after coach review. |
| autocode_sessionB | Save or load an autocoding session. action=save: persist state to file. action=load: restore state from file. |
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 4 tools
autocode, autocode_turn, and autocode_session all relate to the same autocoding workflow, which creates moderate overlap—autocode handles the high-level entry points while the others handle sub-parts, but an agent might confuse 'autocode' with 'autocode_turn' since both generate prompts. dialectic is clearly distinct. The separation of concerns is mostly clear but the naming makes the boundaries less obvious than they could be.
All names are lowercase single words in snake_case convention, which is consistent. However, dialectic does not follow the verb-oriented pattern (autocode is a verb-noun, autocode_turn is a verb-noun, autocode_session is a verb-noun, but dialectic is a bare noun), making it the outlier in style.
Four tools for a reasoning/coaching paradigm server is a reasonable, focused scope. Each tool addresses a distinct slice (dialectic reasoning, autocoding orchestration, step execution, session persistence), and none feel redundant or extraneous.
The dialectic tool covers the reasoning workflow well, and the autocoding trio covers init, workflow, single-step execution, and session persistence. However, there's no session-management tool for the dialectic workflow (only autocode has save/load), and no explicit mechanism for resetting or inspecting sessions, which are notable gaps.