No user-submitted related servers found.
Scored across 118 tools
Many tools have overlapping or unclear boundaries, such as the multiple transport configuration tools (transportConfigurations, getTransportConfiguration, setTransportsConfig, createTransportsConfig, hasTransportConfig) and the numerous debugger tools with similar names (debuggerListeners, debuggerListen, debuggerAttach, debuggerVariables, debuggerChildVariables). The mix of generic operations like loadTypes, objectTypes, and collectionFeatureDetails also creates ambiguity.
Naming is inconsistent: some tools use camelCase (adtDiscovery, loadTypes, syntaxCheckCode), some use snake_case (unLock, setObjectSource), and some use mixed patterns (createTransportsConfig vs transportConfigurations). Verb placement varies (transportDelete vs deleteObject, gitCreateRepo vs createTransport), and there is no consistent verb_noun or noun_verb convention.
118 tools is far beyond the typical well-scoped server range. The server attempts to cover ADT discovery, transports, debugging, Git, ATC, traces, refactoring, and more, resulting in a sprawling surface that is difficult to navigate. This extreme count suggests the server is trying to expose an entire API rather than a curated tool set.
The tool set covers many ABAP development lifecycle areas: source retrieval/editing, activation, syntax checks, transports, debugging, ATC, Git, and traces. However, there are notable gaps and inconsistencies, such as no explicit tool for creating or deleting classes/programs (only validateNewObject and deleteObject), and the transport lifecycle is fragmented across many configuration tools. The breadth is high but the depth per area is uneven.