aiganak-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 | {
"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 |
|---|---|
| query_log_fileB | Executes high-speed DuckDB SQL queries directly against log files (JSONL, CSV, Parquet). |
| inspect_code_astA | Parses a target Python source file into an AST tree to return class, function, and import structures for diagnostic analysis. |
| apply_code_patchA | Safely modifies a target Python source file after validating AST syntax and establishing Git safety gates. Automatically rolls back on invalid syntax. |
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 3 tools
Each tool targets a clearly distinct task: log querying, code inspection, and code modification. There is no overlap between querying logs, parsing ASTs, and applying patches, so an agent would not confuse them.
The naming is inconsistent: query_log_file uses a verb_noun_obj pattern, inspect_code_ast uses verb_noun_obj, but apply_code_patch uses verb_noun. The verbs (query, inspect, apply) are varied and not obviously part of a unified domain vocabulary, and the patterns differ across tools.
Three tools is on the borderline of being too thin for an AIOps server, especially given the mixed domain of log analysis and code modification. The count is defensible, but the scope feels narrow for a server with 'aiops' in its name.
The tools span log querying, code inspection, and code patching, but each area has obvious gaps: there is no tool for writing log query results, no update/get verification for the patch step beyond the patch itself, and the log analysis surface gives no way to define or manage analysis workflows. The domain coverage is fragmented rather than complete.