goal-engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOAL_ENGINE_DB | No | State file path | ~/.goal-engine/goal-engine.sqlite |
| OPENAI_API_KEY | No | Second evaluator fallback | |
| GOAL_ENGINE_HOME | No | Data directory | ~/.goal-engine |
| ANTHROPIC_API_KEY | No | Evaluator fallback when MCP sampling is unavailable | |
| GOAL_ENGINE_EVAL_MODEL | No | Anthropic evaluator model | claude-opus-4-8 |
| GOAL_ENGINE_OPENAI_MODEL | No | OpenAI evaluator model | gpt-4o |
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 |
|---|---|
| set_goalA | Start a run-until-done goal loop. Records the completion condition; the agent should then work toward it and call check_goal at the end of every turn until the goal is met. |
| check_goalA | Evaluate whether the active goal is fully met. Call at the end of every turn with a concrete summary of the work just done. Returns done=true when finished, or done=false plus the specific gap to address next. |
| get_statusA | Inspect the current goal session: condition, turn count, elapsed time, and last evaluation. |
| clear_goalA | End a goal session. Pass completed=true when the goal was verifiably met (used by the self-check fallback); otherwise the session is abandoned. |
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
Each tool has a distinct purpose: set_goal starts, check_goal evaluates, clear_goal ends, and get_status inspects. No overlap or confusion.
All tools follow a consistent verb_noun pattern with underscores (set_goal, check_goal, clear_goal, get_status), making them predictable.
Four tools are exactly right for a goal engine's core lifecycle: start, evaluate, end, and inspect. No unnecessary extras or missing essentials.
The set covers the full lifecycle of a goal session: set, check, clear (with success/failure), and status. No obvious gaps for the intended functionality.