Apache AIops
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.
Governed Apache HTTP Server config, vhost, module and HTTP diagnosis. Every tool is audited and budgeted.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apache_config_includesC | [READ] Show Apache's parsed config include tree with bounded output. |
| apache_compiled_modulesA | [READ] List modules compiled into Apache, excluding dynamic modules. |
| apache_static_directivesC | [READ] List directives from Apache's static modules with bounded output. |
| apache_buildC | [READ] Show Apache build options and compiled paths. |
| apache_runtime_configC | [READ] Dump Apache's parsed runtime configuration. |
| apache_server_statusB | [READ] Get bounded machine-readable mod_status metrics from configured URL. |
| apache_error_logC | [READ] Tail an operator-configured Apache error log, with explicit truncation. |
| apache_access_statusB | [READ] Count HTTP statuses in recent common/combined access logs, without raw requests. |
| apache_graceful_reloadB | [WRITE] Config-check then request a graceful reload; outcome needs operator check. |
| apache_versionB | [READ] Get Apache HTTP Server version from apachectl -v. |
| apache_config_checkC | [READ] Run Apache's native config syntax test. |
| apache_vhostsC | [READ] Show Apache's parsed virtual-host mapping. |
| apache_modulesC | [READ] List Apache's loaded modules. |
| apache_probeB | [READ] GET the configured health URL without downloading its body. |
| apache_diagnoseC | [READ] Correlate version, config, vhosts, modules and optional HTTP probe. |
| undo_listA | [READ] List recorded, not-yet-applied undo tokens (most recent first). Each entry names the original tool, the inverse tool that One extra row is read so Each entry carries Args: limit: Max rows to return (default 50, capped at 500). target: Unused (undo state is host-local); accepted for CLI uniformity. |
| undo_applyA | [WRITE][risk=medium] Apply a recorded undo by dispatching its inverse tool. The inverse runs through its own governed tool, so it is audited under its own risk tier. Pass dry_run=True to preview the inverse call without executing it. A token can only be applied once. Args:
undo_id: The undoId from undo_list (or an |
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 17 tools
Most tools target distinct diagnostic facets such as build info, loaded vs compiled modules, access logs, error logs, server status, and probes. There is some overlap among apache_runtime_config, apache_static_directives, apache_config_includes, apache_vhosts, and apache_diagnose, but the descriptions and aggregate-vs-specific framing make selection reasonably clear.
The Apache domain tools consistently use an apache_ snake_case prefix, and the undo helpers use a consistent undo_ prefix. The mixed prefix families are logical rather than chaotic, though the set is not a single uniform verb_noun pattern.
Seventeen tools is slightly above the ideal compact range, but the surface spans several legitimate Apache diagnostic areas: config, modules, vhosts, logs, status, reload, and undo. Each tool has a plausible operational role rather than being redundant filler.
The set covers key Apache AIops workflows: version/build inspection, config checking, module and vhost discovery, log/status inspection, diagnosis, graceful reload, and undo support. It lacks broader service lifecycle controls such as start/stop/restart and config mutation, but those are minor gaps for a primarily diagnostic server.