astra-ops-hub
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_casesA | List the 19 Astra Ops Hub use-case engines |
| run_caseC | Execute one use-case engine against the Northlamp world fixture |
| run_allB | Execute every engine and record memory plus focus areas |
| monitorC | Heartbeat: statuses and open approval gates |
| memory_recentD | Read evolution memory |
| focus_directivesD | Directives learned from competitor gaps |
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 largely distinct role: listing cases, running one vs. all engines, checking status, reading memory, and reading directives. The only mild overlap is between run_all and run_case, but their descriptions make the scope difference clear.
All names use snake_case, but the conventions are mixed: list_cases and run_case are verb_noun, run_all is verb_adverb, monitor is a bare verb, while memory_recent and focus_directives are noun phrases. Readable but not a predictable pattern.
Six tools is well-scoped for an ops hub covering listing, execution, monitoring, and memory/directive reads. Each tool earns its place without bloat or excessive thinness.
Core execution and inspection paths exist, but the surface has notable gaps: monitor exposes open approval gates yet there is no approve/reject tool, and there is no way to inspect a single engine's details or status. Memory and directives are read-only, which may be acceptable but limits lifecycle coverage.