MCP server for SAP ABAP development via ADT — read, write, activate, run, debug, and undo via a local write journal (writes opt-in, package allowlist)
abapsmith defines 25 tools for SAP ABAP development. Tool names follow verb_noun convention (abap_read, abap_write, abap_activate) which is good. However, critical gaps undermine quality: (1) No visible input schemas in provided source, tool definitions appear to exist but parameter schemas are not shown, making validation impossible. (2) Descriptions are present but minimal (10-50 chars typically), lacking WHEN/WHY context needed for LLM selection. (3) No documented output schemas visible. (4) Error handling code exists (tool-errors.ts) but tool-level recovery guidance is absent. (5) Many tools combine multiple concerns (abap_ui 'interact with SAP UI screens' is vague; abap_enhancement 'work with ABAP enhancements' lacks specificity). Per-tool analysis shows consistent structural gaps across the 25 tools.
Activate ABAP objects
Run ABAP Test Cockpit (ATC) checks
Work with SAP BOPF (Business Object Processing Framework)
Test BOPF objects
Preview ABAP data
Debug ABAP programs
Query ABAP runtime dumps
Work with ABAP enhancements
Execute fluid ABAP tools
No input schemas visible for any of 25 tools. Parameter definitions, types, and constraints cannot be verified. This violates pattern:constrained-input and pattern:tool-description.
Tool descriptions are minimal (10-50 chars), lacking WHEN/WHY context. E.g., 'Read ABAP source code and metadata' does not explain when to use abap_read vs abap_search, or what metadata is returned. Violates pattern:tool-description baseline of 50-200 chars.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 29 | <=2025-11-25 | v2 |
Work with SAP Fiori Page Mapper (FPM)
Work with SAP IMG (Implementation Guide)
Edit SAP IMG activities
Manage write journal for undo operations
Query locked ABAP objects
Open SAP GUI URLs
Apply ABAP quick fixes
Read ABAP source code and metadata
Execute ABAP programs and classes
Search ABAP objects and code
Work with ABAP services
Run ABAP unit tests
Manage ABAP execution traces
Manage ABAP transport requests
Interact with SAP UI screens
Write ABAP source code with journal tracking
No documented output schemas. LLMs cannot plan downstream tool calls or extract required fields (e.g., does abap_search return object_id, object_name, object_type?). Violates pattern:response-shaper.
Vague tool names and descriptions conflate multiple concerns. E.g., abap_ui 'Interact with SAP UI screens' is ambiguous, does it click buttons, read fields, or navigate? abap_enhancement 'Work with ABAP enhancements' lacks specificity. Violates pattern:tool naming clarity.
Error handling code exists (tool-errors.ts) but tool-level recovery guidance is absent. LLMs cannot determine if errors are retryable or user-fixable. Violates pattern:recovery-guide.