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

GatewayListSystems

Read-onlyIdempotent

Lists configured SAP systems and their modes so you can see where writes are allowed, reads and tests run, or read-only access applies before calling tools.

Instructions

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.

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": "GatewayListSystems"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely new behavioral context: the dev/qas/prd permission model and the fact that enforcement is decided per call and surfaced as MODE_FORBIDDEN, which tells the agent how write attempts can fail.

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 core action is front-loaded in the first clause, and the mode vocabulary that follows is dense but load-bearing for interpreting the output. The embedded 'Available: (none configured)' is a runtime snapshot baked into static text, which slightly muddies rather than clarifies, but overall there is little waste.

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 no output schema, the description carries the burden of describing the return value, and it does: a list of configured systems, each with a mode, plus the meaning of each mode. What is missing is the shape of the response (fields, ordering) and whether the 'none configured' state is a live value, but for a zero-argument read tool this is close to sufficient.

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?

There are zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object and the description correctly does not invent arguments.

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

Purpose4/5

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

The description opens with a concrete verb and resource: 'List the configured SAP systems with their mode.' An agent can distinguish this inventory operation from GatewayListTools and GatewayCallTool without opening any schema, though the description never explicitly names those siblings as alternatives.

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

Usage Guidelines3/5

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

Usage is only implied: describing dev/qas/prd modes and the MODE_FORBIDDEN outcome hints that this is the discovery step before calling a gateway tool, but the description never says 'call this before GatewayCallTool' or states when not to use it. The reader must infer the workflow ordering.

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