Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap List Connections

sap_list_connections
Read-only

Lists open SAP connections and sessions across SAP Logon and SAP Business Client, showing system, client, user, transaction, session number, and window title.

Instructions

List all open SAP connections and sessions.

Covers SAP Logon plus SAP Business Client / embedded SAP GUI sessions (host: saplogon | sapguiserver). A connection with no sessions and scripting_disabled: true means the server parameter sapgui/user_scripting is off, so no session can be read. Each session has its system, client, user, transaction, session_number (the "(2)" in "DEV(2)") and window title.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Consistent with readOnlyHint=true / destructiveHint=false, and it adds real context beyond annotations: what `host` values appear, and that a connection with no sessions plus `scripting_disabled: true` means sapgui/user_scripting is off so no session can be read — a diagnostic failure mode an agent would otherwise misread as an empty result. It does not mention ordering, limits, or what happens if no SAP GUI is running.

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 one-line purpose, then two short paragraphs of scope and interpretation. The parenthetical `("(2)" in "DEV(2)")` is a useful concrete anchor rather than filler, though the paragraph on session fields is slightly dense.

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 params, an output schema, and read-only annotations, the description supplies everything needed to call and interpret the tool, including the scripting-disabled caveat. The only missing piece is a next-step pointer (which sibling to call after listing).

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?

Zero parameters, so the baseline is 4; the description still pre-explains the `host` discriminator values and the per-session fields, which primes interpretation of the result rather than the call.

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?

Specific verb+resource: "List all open SAP connections and sessions", with the scope widened explicitly to SAP Logon and Business Client / embedded SAP GUI sessions via the `host` values. It does not name a sibling (e.g. sap_connect, sap_get_session_info) to sharpen the boundary, so it stops short of a 5.

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: an agent infers this is the discovery/enumeration step before selecting a session, and that `scripting_disabled: true` signals a troubleshooting condition. There is no explicit when-to-use/when-not or pointer to the alternative tools (sap_connect_existing, sap_get_session_info).

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

Deploy Server

Other Tools