Skip to main content
Glama

Sap List Connections

sap_list_connections

Lists available SAP systems, separating configured systems from SAP Logon connections so you can pick the correct system key to log in.

Instructions

List available SAP systems. Returns two sections: 'configured_systems' from systems.json (pass the 'key' field as system_key to sap_login), and 'connections' from SAP Logon (SAPUILandscape.xml, Desktop only). IMPORTANT: pass a configured_systems 'key' as system_key to sap_login, NOT a SAP Logon entry name. If configured_systems is empty, check config_error.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
connectionsNo
config_errorNoWhy systems.json could not be loaded (e.g. an unsupported language). None when the config is valid or no config file exists.
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
configured_systemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose real behavior: the two-section return shape, the underlying file sources (systems.json, SAPUILandscape.xml), a Desktop-only platform limitation, and the existence of a config_error field when configured_systems is empty. It does not mention permissions, whether results are cached/refreshed, or that the tool is strictly read-only, but the important operational caveats are surfaced.

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?

Front-loaded with the purpose, then the return sections, then the critical warning — good ordering with no filler. There is minor redundancy between the parenthetical about passing 'key' as system_key and the later 'IMPORTANT' sentence covering the same instruction, which keeps it from a 5.

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

Completeness5/5

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

For a zero-parameter lister with an output schema and no annotations, this covers everything an agent needs: what it returns, where each section comes from, which value to reuse downstream, the Desktop-only caveat, and what to check when the primary section is empty.

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?

The tool takes zero parameters, so the baseline is 4, and the description sensibly spends that space explaining the semantics of the 'key' field in the response rather than a param. That cross-references precisely what the agent must extract and forward to sap_login.

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 ('List available SAP systems') and immediately clarifies that the result mixes two distinct sources, configured_systems from systems.json and connections from SAP Logon. It also names the sibling it feeds (sap_login), so an agent can distinguish it from session or capability tools without opening a schema.

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

Usage Guidelines4/5

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

Strong workflow guidance: it tells the agent to take a configured_systems 'key' and pass it to sap_login, and explicitly warns against using a SAP Logon entry name. What's missing is an explicit statement that this should be called before sap_login or guidance on when connections entries are usable at all; the guidance is clear context but stops short of full when/when-not framing.

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