platform-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROM_URL | Yes | The URL of the Prometheus server (e.g., http://localhost:9091 after port-forward) | |
| GOLDEN_PATH_CATALOG | Yes | Absolute path to the golden-path-portal catalog.json file |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tenantsA | Liste les namespaces tenants de multi-tenant-platform, avec leur niveau de PodSecurity applique. |
| get_tenant_podsA | Liste les pods d'un tenant donne avec leur statut et leur nombre de redemarrages. |
| get_tenant_sloA | Recupere la disponibilite (SLI), l'error budget restant et la latence p95 d'un tenant, via les recording rules Prometheus de multi-tenant-platform. Necessite un port-forward actif vers Prometheus. |
| list_argocd_applicationsA | Liste les Applications ArgoCD avec leur statut de synchronisation et de sante. |
| get_chaos_schedulesA | Liste les Schedule Chaos Mesh actives d'un tenant (recurrence, type d'experience). |
| list_catalog_servicesA | Liste les services enregistres dans le catalogue du golden-path-portal. |
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 targets a distinct resource (tenants, pods, SLO, ArgoCD applications, chaos schedules, catalog services) with clear descriptions. Even the tenant-specific tools (pods, SLO, chaos schedules) are differentiated by the resource they return, so there is minimal ambiguity.
The naming generally follows a list_/get_ prefix with resource names, but the pattern is not perfectly consistent: list_ is used for global resources while get_ is used for tenant-specific ones, and get_chaos_schedules omits 'tenant' from its name. Despite this minor deviation, the verb_noun structure is recognizable.
Six tools is a well-scoped number for a read-only platform observability server. The set covers the main platform resources without unnecessary bloat, and each tool serves a distinct purpose within the apparent domain.
The tool set covers listing and basic tenant-scoped queries but lacks any single-resource detail views (e.g., a specific ArgoCD app or catalog service) and any management/mutation operations. This limits the surface to read-only inspection, which may be intentional but leaves notable gaps for a 'platform' server.