runner-fleet-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fleet_statusB | Return the latest read-only runner fleet snapshot. |
| get_slo_reportB | Return current SLO checks and breaches without changing infrastructure. |
| recommend_runner_capacityB | Calculate advisory runner capacity; this tool never scales resources. |
| list_recent_incidentsC | List recent synthetic SLO-breach reports and failure evidence. |
| get_cost_estimateB | Return the latest synthetic runner-compute estimate and exclusions. |
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 targets a distinct concern (fleet status, SLO checks, capacity advice, incidents, cost). The main overlap is between get_slo_report (current breaches) and list_recent_incidents (recent breach reports), but descriptions clarify the temporal and evidentiary distinction.
All names use snake_case with a clear verb_noun pattern (get_fleet_status, list_recent_incidents, recommend_runner_capacity). The verbs get/list/recommend are appropriate and consistently ordered.
Five tools is well-scoped for a read-only advisory server covering fleet status, SLOs, capacity, incidents, and cost. No tool feels redundant or missing at this count.
The read-only advisory surface covers the main observability areas (status, SLOs, capacity, incidents, cost). Minor gaps exist for drill-down details (e.g., per-runner information or historical trends), but core agent workflows are supported.