F5 Cloud Status MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| f5-status-get-overallB | Get the current overall status of F5 Cloud services including operational state and service health indicator |
| f5-status-get-componentsC | Get all F5 Cloud service components with their current operational status, organized by category (Distributed Cloud Services, XC App Stack, etc.) |
| f5-status-get-componentC | Get detailed information about a specific F5 Cloud service component by ID or name |
| f5-status-get-incidentsC | Get current and recent incidents affecting F5 Cloud services, including status updates and affected components |
| f5-status-get-maintenanceC | Get scheduled, active, and upcoming maintenance windows for F5 Cloud services |
| f5-status-searchA | Search F5 Cloud status information by keyword or pattern, including components, incidents, and maintenance |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity: get-component targets a specific item, get-components lists all, get-incidents focuses on incidents, get-maintenance on maintenance, get-overall on overall status, and search enables keyword queries. The descriptions reinforce these boundaries, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with the prefix 'f5-status-', such as 'f5-status-get-component' and 'f5-status-search'. This uniformity enhances readability and predictability, with no deviations in style or convention.
With 6 tools, the server is well-scoped for monitoring F5 Cloud status, covering key aspects like components, incidents, maintenance, overall status, and search. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides complete coverage for status monitoring, including CRUD-like operations (get/list for components, incidents, maintenance) and additional utilities (overall status and search). There are no obvious gaps, enabling agents to handle typical workflows without dead ends.