Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Get Session Info

sap_get_session_info
Read-only

Retrieves current SAP session details—system, client, user, transaction, and screen—plus SAP GUI version and read-only scripting status to confirm whether write actions are allowed.

Instructions

Get information about the current SAP session (system, client, user, transaction, screen).

Also the SAP GUI release (sap_gui_version) and scripting_read_only: when true, the SAP server allows read-only scripting and write tools refuse.

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

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.9/5.0
Behavior4/5

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

Annotations already cover the read-only safety profile, and the description adds genuinely useful behavioral context beyond them: the scripting_read_only flag's semantics and the consequence that write tools refuse when it is true. It does not state what happens if no connection exists, which is a remaining behavioral gap.

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 purpose is front-loaded in the first sentence and the second sentence explains a non-obvious flag that would otherwise confuse a caller. The phrasing 'Also the SAP GUI release...' is slightly disfluent, but every element earns its place.

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 read with an output schema and read-only annotations, this covers what an agent needs: what it returns and the critical scripting_read_only gate on write tools. Return-value details are correctly delegated to the output schema.

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 per the rubric. The description additionally names the data points returned, adding light value over an empty schema, though the output schema already carries the return contract.

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?

States a specific verb and resource ('Get information about the current SAP session') and enumerates the returned facets (system, client, user, transaction, screen), which implicitly distinguishes it from sap_get_screen_info. It stops short of explicitly naming the sibling it differs from, so an agent must infer the boundary.

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: 'current SAP session' suggests an already-established connection, and the scripting_read_only note hints at a pre-flight check before write operations. There is no explicit when-to-use/when-not guidance or reference to sap_connect / sap_connect_existing for the not-yet-connected case.

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