Skip to main content
Glama

Sap Session Release

sap_session_release

Releases an agent binding from an SAP GUI session so the session can be reused by other agents or general users. Use when work is finished and the session should become available.

Instructions

Release agent binding from a session. Use when an agent finishes work and wants to free the session for other agents or general use.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "sap_session_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession ID to release

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
session_idNoID of the session that was released
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
released_agentNoAgent that was unbound, if any

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the key behavioral outcome that the session becomes available to other agents or general use. It does not state whether the session itself stays alive, what happens on a failed release, whether the call is idempotent, or what permissions are required.

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?

Two sentences, zero waste; the action is stated first and the usage condition follows immediately. Nothing needs trimming or reordering.

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?

For a simple one-parameter tool with an output schema covering return values, the definition covers purpose and the main usage trigger adequately. The remaining gap is behavioral edge cases (failure modes, effect on concurrent bindings) rather than anything structural.

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

Parameters3/5

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

Schema description coverage is 100% for the single required session_id, so the schema already documents the parameter. The description adds nothing about the identifier's format, provenance, or behavior when an unknown or already-released ID is passed.

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 uses a specific verb and resource ('Release agent binding from a session'), so the operation is unambiguous. It does not distinguish itself from close-proximity siblings such as detach, close, or reset_to_primary, which an agent could easily confuse with release.

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?

It gives a clear triggering condition: use it when an agent finishes work and wants to free the session for other agents or for general use. It offers no explicit when-not guidance or named alternative for cases where the session should be closed or reset instead.

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