Explorative Tools

Explorative Tools

This tools enable the agent to do a developer-focuesd research in a SAP system.

Available MCP Tools

Tool Name	Description
sap_execute_request	Executes a raw, arbitrary HTTP request directly against the SAP backend utilizing the active CSRF vault tunnel.
sap_execute_sql	Executes a raw, arbitrary OpenSQL query (e.g. SELECT DISTINCT) directly on the SAP backend via HTTP POST. - Usage: Strongly recommended over sap_select_data when aggregations, joins, or distinct parameters are required. - Limits: Use max_rows to prevent memory bloat.
sap_explore_domain	Explores the SAP repository bi-directionally starting from an Object, Package, or Application Component. In mode 'bottom_up', crawls from the target up to its Application Component. In mode 'top_down', expands a Package or Component to show immediate children with descriptions.
sap_fetch_source	Retrieves the live textual ABAP source code (or XML representation) of a structural SAP object directly from the native ADT server. If the file is too large and spills over to ./tmp/, you MUST use sap_ast_query to extract the code and sap_ast_replace to mutate it.
sap_find_badi	Navigates the SAP dictionary to extract a complete BAdI chain (Extension Spot -> BAdI Definition -> Implementations -> Interfaces -> Implementing Classes). You can pass ANY anchor in the chain (e.g. ZCL_IMPL).
sap_get_element_info	Retrieves semantic object mappings for ABAP inline declarations and explicitly referenced types dynamically like Eclipse F2 Help. Send the context ABAP block coupled to the exact line and character offset.
sap_get_object_outline	Retrieves a precise JSON architectural outline mapping attributes, method boundaries, properties, and signatures of an SAP object via its ADT objectstructure endpoint without loading its entire source code.
sap_get_type_hierarchy	Retrieves the structural class/interface hierarchy (superclasses, subclasses, implementing classes) from ADT.
sap_list_package	Lists all developmental objects contained within an SAP package recursively.
sap_map_dependencies	Walks the ABAP AST to map physical structure dependencies (Database Tables, Function Modules, referenced Classes/Types). Returns a JSON architecture blueprint for the AI to trace with sap_where_used before refactoring.
sap_resolve_customizing_path	Resolves the reverse SPRO navigation paths for a given customizing table or view.
sap_resolve_frontend_target	Structurally decodes frontend coordinates (TCODEs, SPRO nodes, or Easy Access menus) into physical backend entities. Translates an end-user documentation coordinate into its underlying execution Program, Terminal TCODE, or SM30 Maintenance View.
sap_search_objects	Executes a native ADT Information System search (Find-by-Name) using wildcards. - Output: Returns an array of object references matching the query. - Limits: Use max_results to clamp payload size.
sap_select_data	Selects data directly from SAP tables using the native ADT Data Preview endpoint. - Usage: Ideal for quick, flat-table extraction. For aggregations or complex joins, use sap_execute_sql instead.
sap_where_used	Executes a native SAP Where-Used query to resolve backward-link dependencies. - Output: Returns an array of references mapping parent packages and owners. - Usage: Vital for tracing cross-component impact before refactoring (e.g. who calls this class, who uses this message).