Model Context Protocol server for Prometheus integration with multi-tenant support
Single tool 'list_tenants' with empty input schema and minimal description. No parameter documentation, no output schema specification, no error handling guidance. Tool definition is visible in server.py but lacks the structured metadata required for LLM-driven agent composition. Description is 34 chars (below 50-char baseline for clarity). No input validation, no pagination support despite multi-tenant context suggesting potential for large result sets.
List all configured Prometheus tenants
Input schema is empty object {}, no parameters documented, no constraints, no types.
Tool description is 34 characters ('List all configured Prometheus tenants'), below 50-char minimum for LLM clarity.
No output schema documented. LLMs cannot infer what fields to expect (tenant names, URLs, credentials, org_ids, etc.). Breaks downstream tool chaining.
No pagination support (limit, offset, page_size). Multi-tenant configs could return hundreds of tenants; unbounded results blow context windows.
No error handling guidance. What if tenant config is malformed? What if Prometheus is unreachable? LLM receives no recovery path.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | <=2025-11-25 | v2 |