aiops-mcp
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 |
|---|---|
| drift_scanB | Compute drift findings: observed facts versus the known-good baseline. |
| fact_historyA | Return the full recorded (bitemporal) history of facts for a subject. |
| ingest_observationA | Parse captured host telemetry into observed facts. |
| query_factsA | List active fleet-state facts; filter by subject and/or fact_type. |
| run_actionB | Run a tier-gated actuation via an adapter (DRY_RUN, approve, execute). |
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 5 tools
Each tool has a distinct purpose: ingest_observation creates facts, query_facts retrieves them, fact_history shows historical data, drift_scan computes differences, and run_action executes actuations. No overlap.
All names use snake_case and are two-word phrases, but they mix verb_noun (e.g., ingest_observation, query_facts) and noun_noun (e.g., drift_scan, fact_history) patterns. Still consistent in style and readable.
With 5 tools, the set covers the essential AIOps operations—observation ingestion, fact querying and history, drift detection, and action execution—without being excessive or sparse.
Covers the main lifecycle: ingest, query, history, drift, and action. Missing update/delete for facts or baseline management, but core workflows are supported.