Maintenant
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| acknowledge_alertA | Acknowledge an active alert so it stops escalating. |
| create_channelA | Create a notification channel. The webhook type is open in every edition; email needs Personal, slack needs Pro, teams needs Pro, telegram needs Personal. |
| create_escalation_policyC | Create a new escalation policy. Requires the Pro edition. |
| create_incidentB | Create a new incident on the status page. Requires the Personal edition. |
| create_maintenanceA | Schedule a maintenance window on the status page. Requires the Pro edition. |
| create_triggerB | Create a new alert trigger, notifying recoveries by default. Scope filters require the Personal edition. |
| delete_channelB | Delete a notification channel. Triggers and escalation levels pointing at it lose that destination. |
| delete_escalation_policyA | Delete an escalation policy and stop any active runs. Requires the Pro edition. |
| delete_triggerB | Delete an alert trigger. The linked channels are not deleted. |
| get_channelA | Get a single notification channel by ID, with its delivery health and the triggers routing to it. Header values are masked as *** and Slack, Discord and Teams webhook URLs are cut after the host; the secret is never returned. |
| get_containerA | Get detailed information about a specific container including state, health, image, labels, and recent state transitions. |
| get_container_logsB | Get recent log lines from a container's stdout/stderr output. |
| get_editionA | Report the running edition, which capability each edition opens, the quota usage of capped resources, and the resource-history windows. Call this before offering a feature that may be gated, instead of asking the operator which edition they run. |
| get_endpoint_historyA | Get detailed check history for a specific endpoint, including response times, status codes, and error messages. |
| get_escalation_policyA | Get a single escalation policy by ID. Requires the Pro edition. |
| get_escalation_runA | Get full detail of an escalation run including all deliveries. Requires the Pro edition. |
| get_healthA | Check maintenant's own health status, version, and runtime information. |
| get_resourcesA | Get current host resource metrics summary including CPU usage, memory usage, network throughput in bytes per second (net_rx_rate, net_tx_rate), and disk usage. |
| get_security_insightsA | List security insights (dangerous runtime configurations) across containers, or for a single container. Includes a severity summary. |
| get_security_postureA | Get the infrastructure security posture score, or the posture of a single container. Requires the Personal edition. |
| get_swarm_infoA | Get Docker Swarm cluster info (manager/worker counts, whether this node is a manager). Reports inactive when Swarm is not detected. |
| get_top_consumersB | Get containers ranked by resource consumption (CPU or memory), useful for identifying resource-heavy containers. |
| get_triggerA | Get a single alert trigger by ID. |
| get_updatesA | List available image updates for monitored containers, and the operating system of every monitored host with its end-of-support status (supported, ending_soon, ended, unknown, untracked) and dates. |
| list_agentsA | List all registered remote agents with their connection state, runtime type, hostname, and label. Requires the Personal edition. |
| list_alert_escalation_runsA | List escalation runs attached to a specific alert. Requires the Pro edition. |
| list_alertsA | List alerts. By default returns only active (unresolved) alerts that are not yet acknowledged. Set active_only to false to return the last 100 alerts instead, acknowledged, resolved and silenced ones included. |
| list_certificatesA | List all monitored TLS certificates with expiration dates, issuer, chain validity, and days until expiry. |
| list_channelsA | List notification channels. Channels are silent on their own: an alert reaches one only through an alert trigger or an escalation level. Header values are masked as *** and Slack, Discord and Teams webhook URLs are cut after the host; the secret is never returned. |
| list_containersB | List all monitored containers with their current state (running, stopped, restarting), health status, and basic metadata. |
| list_cveA | List active CVE vulnerabilities detected in container images, optionally filtered by container or minimum severity. For a single container the response carries the CVE evaluation state: an empty list only means "no known CVEs" when the state is "evaluated". Requires the Personal edition. |
| list_endpointsA | List all monitored HTTP/TCP endpoints with their current status (up/down), response time, and uptime percentage. |
| list_escalation_policiesA | List all escalation policies with their filters and levels. Requires the Pro edition. |
| list_heartbeatsA | List all heartbeat/cron monitors with their current status, last ping time, expected period, and grace period. |
| list_kubernetes_namespacesA | List Kubernetes namespaces known to maintenant across monitored clusters. |
| list_kubernetes_nodesA | List Kubernetes nodes with their roles, conditions, capacity and running pod counts. |
| list_kubernetes_podsA | List Kubernetes pods with their status, restart count and node, optionally filtered by namespace, workload, node or status. |
| list_kubernetes_workloadsA | List Kubernetes workloads (Deployments, StatefulSets, DaemonSets...) grouped by namespace, with ready/desired replica counts and status. |
| list_risk_scoresA | List image update risk scores per container (0-100) with their risk level. Requires the Personal edition. |
| list_swarm_nodesA | List Docker Swarm nodes with their role, status, availability and task count. |
| list_swarm_servicesB | List Docker Swarm services with their image, mode, and desired/running replica counts. |
| list_swarm_tasksA | List Docker Swarm tasks (the running units of a service), optionally filtered by service, with their state and node. |
| list_triggersA | List all alert triggers (filter rules + channel destinations). |
| pause_monitorA | Pause a heartbeat monitor to temporarily stop alerting. Only heartbeat monitors are supported. |
| resume_monitorA | Resume a paused heartbeat monitor. Only heartbeat monitors are supported. |
| set_escalation_policy_activeA | Activate or deactivate an escalation policy; deactivating it stops its running escalations. Requires the Pro edition. |
| test_channelA | Send a test notification through a channel and report whether it was delivered. |
| update_channelA | Update a notification channel. Omitted fields keep their stored value; a stored secret is never cleared this way. |
| update_escalation_policyB | Update an existing escalation policy (name, filters, levels, active). Requires the Pro edition. |
| update_incidentA | Post a status update to an existing status page incident. Requires the Personal edition. |
| update_triggerB | Update an existing alert trigger (last-write-wins). Scope filters require the Personal edition. |
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 51 tools
Most tools are cleanly separated by resource + action (list_containers/get_container/get_container_logs, swarm vs kubernetes vs endpoint resources). A few clusters come close: get_security_insights vs get_security_posture, and get_updates vs list_cve vs list_risk_scores all touch image risk from different angles. Descriptions disambiguate these well, so collisions should be rare.
Every tool follows a strict snake_case verb_noun pattern (list_*, get_*, create_*, update_*, delete_*, plus set_/pause_/resume_/acknowledge_/test_ verbs used deliberately). No camelCase or stylistic drift anywhere in the 51 names.
51 tools is heavy even for a multi-domain monitoring platform, and several families could be consolidated (six escalation-policy tools, three swarm list tools, four kubernetes list tools, four image-risk tools). Many tools also differ only by a boolean filter that could be a parameter, inflating the surface an agent must scan.
Full lifecycle exists for channels, triggers, and escalation policies, but there are notable dead ends: alerts can be listed and acknowledged but not resolved or silenced despite silenced state existing; heartbeats and endpoints can be listed/paused but not created; incidents and maintenance can be created but not listed, resolved, or cancelled.