Skip to main content
Glama
abap-adt-mcp-gateway
by lusmjs

GatewayListTools

Read-onlyIdempotent

Search the ABAP ADT contract by group, name pattern, verb, or free text to discover a tool, then call it with GatewayCallTool.

Instructions

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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "GatewayListTools"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoRequired when detail is "schema".
verbNoOnly tools starting with this verb: Create, Read, Get, Update, Delete, Check, Activate, Search, …
groupNoOnly this group. Groups partition the contract: every tool has exactly one.
limitNoMaximum entries to return (default 200).
queryNoFree text matched against name and description (case-insensitive).
detailNoDefault "names".
systemNoList only what this system allows. Omit to see the union over every configured system; a name listed here can still be refused for another system.
patternNoWildcard over the tool name, e.g. "Get*", "*Program*", "*Low".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real context: the contract size, that these three tools are the only advertised ones, and what each detail level reveals. It omits one meaningful trait — with 336 tools and a default limit of 200, results can be silently truncated, and nothing warns about that or about result ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The discovery workflow is front-loaded and followed by the detail-mode options, with no filler sentences. The trailing 'detail:' fragment is slightly compressed and reads like a notation rather than prose, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight optional parameters and no output schema, the description does enough: it explains the discovery workflow, the filtering axes, and the detail levels. The remaining gaps are how limit interacts with the 336-tool catalog and what shape results take when detail is "names" versus "schema".

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the enum labels by explaining that "descriptions" adds group and effect while "schema" returns the full input schema of one tool. That clarifies what the returned payload contains, which the raw enum values alone do not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (search the 336-tool contract) and enumerates the search axes: group, name pattern, verb, free text. It also positions itself against siblings by naming GatewayCallTool as the follow-up action, so an agent knows instantly this is the discovery entry point rather than an invocation tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit workflow: only three gateway tools are advertised, so a tool must be found here first and then invoked with GatewayCallTool. The three detail modes are described inline, which tells the agent which mode to pick for a name list versus a schema lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.