MCP Wrapper for SAP Plant Maintenance Portfolio - provides HTTP endpoints to query maintenance orders from SAP CAP backend via OData service
Single tool with minimal definition quality. Tool name 'get_maintenance_orders' follows verb_noun convention (+), but description is generic (67 chars, below 100-char minimum for clarity). Input schema present but parameters lack type constraints (no enums for priority/status despite being filter fields). No output schema documented. No error handling guidance. No parameter validation rules or format constraints. Tool appears to be a simple HTTP wrapper without LLM-optimized design patterns.
Fetch maintenance orders from OData service with optional filtering by priority and status
No output schema documented. LLM cannot plan downstream operations or extract required fields (e.g., order IDs for follow-up actions).
Parameters 'priority' and 'status' lack enum constraints. Free-form strings invite hallucinated values (e.g., 'URGENT' vs 'URGENTE'). Should declare valid values as enums.
Description is generic (67 chars). Does not explain WHEN to use this tool vs alternatives, what structure is returned, or prerequisites. Below 100-char minimum for LLM clarity.
No error handling guidance. HTTP 500 response includes only generic 'Failed to fetch' message. LLM cannot determine if error is retryable, user-fixable, or fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
No pagination support. Tool accepts no limit/offset/page parameters. Large result sets will blow context window and degrade LLM reasoning.