Loading ToolBench
Server has 30 tools with schemas and descriptions present, but quality is inconsistent. Most tool descriptions are adequate (50-150 chars), but parameter descriptions are sparse or missing entirely. Many tools lack explicit input validation guidance. Schemas are inferred from test files rather than visible in source code registration. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Error handling is minimal, no recovery guidance or actionable error messages visible. Composition is reasonable (tools are single-purpose), but output schemas are not documented. This is a typical community server with functional definitions but significant polish gaps.
Retrieves ABAP keyword documentation (F1 help)
Activates one or more ABAP repository objects
Checks ABAP syntax for a persisted object (CLAS, INTF, PROG, FUGR)
Removes unused variables and cleans up ABAP source code
Tests connection to the active SAP system
Creates a new ABAP repository object
Creates a new transport request
Tool definitions inferred from test files, not visible in source code registration. Cannot verify actual schema registration in MCP server code.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Agents cannot distinguish safe from dangerous operations.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2025-06-18+ | v2 |
Previews data from a table or view
Deletes an ABAP repository object
Edits a single method in a class
Edits specific spans of source code in an ABAP object
Retrieves detailed information about a data element or domain
Lists objects in a package with optional subpackage inclusion
Searches for OData services and business objects by business term
Lists all configured SAP systems in the landscape
Lists available transport requests
Formats ABAP source code according to SAP standards
Reads the definition of an ABAP message
Reads ABAP repository object source code or metadata
Reads the structure (methods, attributes, interfaces) of a CLAS or INTF
Reads the short dump (runtime error) from the last program execution
Reads field definitions for a table or structure
Releases a transport request
Runs ABAP Test Cockpit (ATC) checks on an object
Executes an ABAP program
Runs unit tests for an ABAP object
Searches for ABAP repository objects by name, type, and package
Switches the active SAP system
Finds where an object is used in the repository
Writes complete source code for an ABAP object
Parameter descriptions are minimal or missing. E.g., 'include' param in read_object lists valid values but does not explain when to use each. 'transportRequest' lacks guidance on when to use $TMP vs explicit request.
No output schemas documented. Agents cannot plan downstream calls or extract required fields (e.g., does search_object return objectName, objectType, packageName, description?). Breaks tool chaining.
No error handling guidance. Tools like delete_object and activate_object have no documented recovery paths. Agents cannot distinguish retryable errors from user-fixable ones.