MCP SAP GUI Server

Overview Schema Source Related Servers Discussions Admin

Sap Disconnect

sap_disconnect

Destructive

Disconnect the current SAP GUI session and release its binding. Closes sessions opened by this MCP connection while leaving manually attached sessions open for continued use.

Instructions

Disconnect from the current SAP session and release the binding.

Closes only the sessions this MCP session opened: the one sap_connect logged on in and any /o window opened from it. Sessions that were attached (via sap_connect_existing), and /o windows opened from them, are detached but left open so the user can continue working manually.

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_disconnect"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructive annotation, the description explains exactly what is destroyed versus preserved: sessions opened by sap_connect are closed, while attached sessions and their /o windows are detached but left open. This is valuable behavioral detail that prevents accidental loss of user work.

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

Conciseness5/5

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

The description is front-loaded with the action in the first sentence, followed by a concise ownership rule. Every sentence adds useful scope information without repetition.

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?

Given that there are no inputs, annotations declare destructive behavior, and an output schema exists, the description is complete enough to call the tool correctly. It supplies the critical session-ownership semantics that annotations alone cannot convey.

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 has zero parameters, so there are no parameter semantics to explain. The baseline for a parameterless tool applies, and the description correctly avoids unnecessary parameter discussion.

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?

The description states a specific verb and resource: disconnect from the current SAP session and release the binding. It is clearly distinct from sibling connection tools such as sap_connect and sap_connect_existing.

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?

The description makes clear which sessions are affected and which are not, implicitly guiding when this tool should be used. It does not name an explicit alternative, but there is only one disconnect operation among the siblings and the ownership rule provides strong context.

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

Deploy Server