Model Context Protocol server for Crossplane control planes. Exposes access to managed resources, composite resources, claims, packages, compositions and their health. Read-only unless writes are enabled.
Server has 5 tools with complete input schemas and descriptions. Naming follows verb_noun convention (crossplane_status, crossplane_managed_resources_list, etc.). All tools have descriptions (34-72 chars, within baseline range). Input schemas are properly typed with descriptions. However, output schemas are not documented in the provided source, and parameter descriptions lack actionable constraints (e.g., enum values for 'status' filter, size constraints for database size). Error handling and recovery guidance are not visible in the tool definitions. The 'crossplane_database_create' tool supports dry-run, which is good for confirmation, but no explicit error classification or recovery patterns are evident.
Create a database resource on the control plane
Diagnose issues with a failing resource
List managed resources with optional status filtering
Show composition tree for a resource
Overall control plane health and status
Output schemas not documented. Tool definitions show input schemas but no documented return types or field structures. LLMs cannot plan downstream calls or extract required data without knowing what fields to expect.
Parameter descriptions lack actionable constraints. 'status' parameter in crossplane_managed_resources_list says 'Filter by status (e.g., not-ready)' but does not enumerate valid values or explain format. 'size' in crossplane_database_create lacks min/max bounds or valid enum values (small, medium, large?).
No error handling or recovery guidance visible in tool definitions. Tools do not document what errors are retryable, what user-fixable errors look like, or how to recover from failures. Agents cannot self-correct.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2025-06-18+ | v2 |
No pagination support visible for list tools. crossplane_managed_resources_list may return unbounded results. Large result sets blow context windows and degrade LLM reasoning. Should support limit and offset/cursor parameters.
Tool descriptions are brief (34-72 chars) and lack WHEN/WHY guidance. 'Overall control plane health and status' does not explain when to call crossplane_status vs crossplane_diagnose, or what the output reveals. LLMs cannot disambiguate similar tools.