data-olympus 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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kb_healthA | Return service health: kb_commit, index_built_at, staleness, degraded flag, and write-side state (pending_count, push_queue_size, last_index_*). verbose: False (default) returns a token-compact shape that keeps the core snapshot and OMITS diagnostic fields that are null/empty (e.g. last_index_error, remote_head_sha when unset). verbose=True returns every field including the nulls. pending_actions, when present, lists open maintenance items (missing
|
| kb_searchA | Full-text search across the KB. Optional tier/category/status/type filters (status e.g. 'active', doc_type e.g. 'decision'). Returns ranked hits with snippets. in_force: when true, HARD-filter to the in-force status class
(active/accepted/approved) AND the validity window (not expired, not
upcoming) before ranking, EXCLUDING superseded/deprecated/expired/
upcoming docs rather than only soft-downranking them. Composes with an
explicit A doc past its abstain: when true, apply the signal gate. If the query matches no
discriminating column (title/tags/applies_when) it is treated as
out-of-scope and the search returns NO hits with verbose: False (default) returns a token-compact shape. Each hit is
{id, title, snippet} plus |
| kb_getA | Retrieve a document by id (STD-U-001, ADR-002, T-NNN, etc.).
Returns the full content markdown plus metadata. Use this when you have a
specific id (from Always resolves regardless of expiry (ids never dangle): an expired
document is still returned, with its full Derivation cues (ids only, for a person to review; nothing is filtered
or demoted because of them): verbose: False (default) returns the full |
| kb_session_recapA | Read-only per-session write summary (issue #112 feedback loop):
N committed, M demoted-to-pending, K rejected for source_session.
Call this (or |
| kb_consultA | Record a consultation for (source_session, workspace) and return the governing rules for the intent. Call before code/architectural work. trigger is 'explicit' (default: a deliberate consult, clears the gate) or 'prompt_hook' (an installer auto-consult: audited, never clears). Retrieval is hard-filtered to the in-force class (active/accepted/ approved, within its validity window, and never a memory-inbox doc): an unreviewed proposed memory, a retired/superseded decision, an expired doc, or a legacy/forged inbox file is never returned as a governing rule. pending_actions, when present, lists open maintenance items (missing
|
| kb_gate_checkA | Return a verdict (allow | consult_required) for a pending code action.
Governed actions require a fresh consultation on record. Records each
check to the audit log (non-destructive; |
| kb_record_eventA | Append a durable, non-destructive audit entry for a client-reported enforcement event. Requires write capability (not a read-only tool). event_type is gate_bypass (agent proceeded despite a gate block) or gate_degraded (kb_gate_check was unavailable; last-known state used). workspace, agent_identity, source_session are required; reason is optional but recommended for gate_bypass entries. Use this when an enforce hook bypassed or degraded the gate and the fallback must be recorded. To check gate status use kb_gate_check; to consult use kb_consult; to read back events use kb_audit or kb_compliance. |
| tool_searchA | Search for tools using natural language. Returns matching tool definitions ranked by relevance, in the same format as list_tools. |
| call_toolA | Call a tool by name with the given arguments. Use this to execute tools discovered via search_tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| onboard | Guided entry point: detect the workspace, then route to project or component onboarding. |
| onboard_project | Guided full-project (T3) onboarding: import, interview, bootstrap, clean up. |
| onboard_component | Guided component (T4) onboarding under a known project. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a fairly distinct role and the descriptions explicitly contrast the closest pairs (kb_get vs kb_search by id vs topic; kb_consult vs kb_gate_check for proactive reading vs per-action verdict; tool_search discovers, call_tool executes). The only mild overlap is consult/gate_check, both of which concern governing-rule compliance, but the guidance for when to use each is explicit.
Seven tools share a clean kb_ prefix with predictable verb/verb_noun forms (kb_get, kb_search, kb_consult, kb_gate_check, kb_health, kb_record_event, kb_session_recap). The two meta-tools (call_tool, tool_search) break the prefix scheme and call_tool is a notably generic name, but overall style is consistent snake_case.
Nine tools is well within a healthy scope for a knowledge-base/governance server, and each named tool maps to a distinct operation (retrieve, search, consult, gate, health, audit-write, recap, plus dynamic discovery/execution). No tool feels like filler.
Several tools explicitly point to operations that are absent from the surface: kb_record_event tells agents to read events back via kb_audit or kb_compliance, kb_search references kb_curate, and kb_session_recap references 'kb pending' — none of which exist here. There is also no document write/curation or status-remediation tool, so the pending_actions maintenance loop the server advertises cannot actually be closed.