clearon-ops-audit-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 |
|---|---|
| get_server_healthB | Report server health and read-only safety boundaries. |
| list_recurring_jobsB | List normalized recurring cron jobs. |
| get_job_healthA | Summarize current health for one job using recovery-aware run evidence. |
| get_recent_failuresB | Return only current latest-run failures within a lookback window. |
| find_missed_or_overdue_runsB | Find enabled recurring jobs whose next-run timestamp is overdue. |
| summarize_degraded_successesA | Find repeated successful runs whose summaries disclose partial, fallback, unavailable, or warning states. |
| check_delivery_failuresC | Separate current intended-delivery failures from execution failures. |
| probe_registered_mcpsB | Safely probe all configured MCPs or a named subset. |
| check_gateway_healthB | Run lightweight gateway health and MCP doctor checks. |
| audit_locksA | Scan only approved workspace roots for actual .lock files. |
| generate_ops_reportC | Compose a read-only scheduler/runtime report from normalized checks. |
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 11 tools
Several tools cluster around health and failure detection—get_server_health/check_gateway_health/probe_registered_mcps overlap in probing MCP/gateway state, and get_recent_failures/check_delivery_failures/find_missed_or_overdue_runs all surface different failure modes. Descriptions clarify the distinctions, but an agent could misroute a health/failure query without careful reading.
All tool names are snake_case and mostly follow a verb_noun pattern, but verb choices are inconsistent: get/list/find/summarize/probe/check/audit/generate are used interchangeably, and check_/get_ overlap semantically. Still readable and object-focused.
11 tools is well within the sweet spot for a specialized read-only ops audit server. Each tool corresponds to a distinct audit concern (health, jobs, failures, MCPs, delivery, locks, reporting) without bloat.
The surface covers the main read-only audit workflow: enumerate jobs, assess job/server/gateway health, surface failures and anomalies, audit locks, and generate a report. Minor gaps like per-tool historical trend endpoints or more granular failure detail are workaround-able.