abap-adt-mcp-gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| GatewayListSystemsA | List the configured SAP systems with their mode. Available: (none configured). A "dev" system accepts writes, a "qas" system reads, tests and checks, a "prd" system reads only — which tool may run where is decided per call and reported as MODE_FORBIDDEN. |
| GatewayListToolsA | Search the contract (336 tools) by group, name pattern, verb or free text. These three gateway tools are the only ones advertised, so this is how a tool is discovered: find it here, then call it with GatewayCallTool. detail: "names" (default), "descriptions" (adds group and effect) or "schema" (the full input schema of one tool). |
| GatewayCallToolA | Call any tool of the contract by name. Arguments are the tool's own arguments; |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct stage of the workflow: discover systems, discover tools, invoke a tool. There is no plausible way to confuse listing systems with searching the contract or calling a tool, and the descriptions reinforce the boundary (find it here, then call it with GatewayCallTool).
All three follow the same predictable Gateway+Verb+Noun pattern (GatewayListSystems, GatewayListTools, GatewayCallTool) with identical PascalCase and prefixing. The shared 'Gateway' prefix also clearly signals these are meta-tools rather than contract tools.
A gateway exposing a 336-tool contract should have a minimal meta-surface, and three tools covers discovery, invocation and context. Each tool earns its place; adding more would bloat the advertised surface and defeat the gateway's purpose.
The lifecycle is closed: list systems, search the contract by group/name/verb/text, then call with schema-on-mismatch error recovery. Minor gaps exist — there is no way to pre-check whether a tool is permitted on a given system without attempting the call, and no dedicated schema/introspection tool separate from the search detail flag.