MCP server for SAP Digital Manufacturing POD2 plugin development — patterns, API reference, REST specs, UI5 docs
Server provides 21 well-named, read-only tools with consistent verb_noun naming (get_, list_, search_). All tools have descriptions (10-200 chars, within baseline 34-392 range). Input schemas are present and typed for all tools. However, parameter descriptions are minimal (often 1-2 sentences), output schemas are not documented, and error handling guidance is absent. No tool annotations (readOnlyHint, destructiveHint) despite all being read-only. Composition is strong, tools chain well (e.g., list_pattern_docs → get_pattern_doc). Security is solid (read-only, no secrets exposed). Naming is clear and action-oriented across all 21 tools.
Class doc – accepts full path or short aliases (`Widget`, `PodContext`, `SfcClient`, …).
API index (all namespaces & classes). Use filter to narrow, e.g. `filter: 'widget'`.
Read source code from a reference extension
Full property list + types + key fields for one entity (case-insensitive)
Read a specific doc. Use `summary: true` for TOC before loading a large file.
This tool - call once at start
Get OpenAPI spec for a service
Get SAPUI5 control documentation with optional section slicing
Output schemas not documented. Tools return data but LLMs cannot infer response structure (field names, types, pagination). Forces agents to guess what fields are available for downstream tool chaining.
No tool annotations despite all 21 tools being read-only. Missing readOnlyHint would help LLMs understand these are safe to call without confirmation and can be retried freely.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | <=2025-11-25 | v2 |
List classes, optionally filtered by namespace
Full server capabilities overview
List all reference example extensions with file structure
List all MDO entities (ORDER, SFC, MATERIAL, ROUTING, BOM, …) with property/navigation counts
List all pattern docs with descriptions
List all available REST API specs
Search across ALL content areas (TF-IDF scored)
Search across all API docs
Full-text search across pattern docs
Search across all entity property names and types
Search endpoints across all APIs
Search across SAPUI5 control library documentation
Full extension validation → VALIDATION-REPORT.md
Parameter descriptions are minimal (1-2 sentences). Lack guidance on expected format, constraints, or when to use optional parameters (e.g., 'summary: true for TOC' is good, but 'filter' and 'offset/limit' lack usage context).
No error handling guidance. Tools lack descriptions of failure modes (e.g., 'entity not found', 'invalid filter syntax'). LLMs cannot self-correct or know when to retry vs. ask user.
Pagination not explicitly documented. Tools like list_api_docs, list_pattern_docs accept offset/limit but no description of total count, next_cursor, or result cap. Large result sets risk context window exhaustion.