Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Execute Transaction

sap_execute_transaction

Execute an SAP transaction code (tcode) to navigate directly to its initial screen. Check the returned screen info and ensure the tcode is permitted by the blocklist or allowlist.

Instructions

Execute (start/run) an SAP transaction code (tcode), e.g. MM03, VA01, SM30.

Navigates to the transaction's initial screen. Always check the screen info in the response to understand what screen you landed on. Some transactions require /n prefix for SCWM (e.g., /n/SCWM/MON). A bare /n leaves the current transaction (unsaved data is lost).

Subject to transaction blocklist/allowlist. Use sap_get_session_info to see the current transaction before navigating away.

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": {
      "tcode": "<tcode>"
    },
    "name": "sap_execute_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
tcodeYes

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?

Adds substantial context beyond annotations: it navigates only to the initial screen, advises verifying the landed screen from the response, documents the SCWM /n/ prefix quirk, and warns that a bare /n discards unsaved data. That last point is in mild tension with destructiveHint=false, but only conditionally, so it reads as helpful disclosure rather than contradiction. Error behavior for blocked transactions is not described.

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 core action, then layered warnings in short paragraphs. Every sentence carries operational value; the multi-line layout is slightly scannable rather than prose-tight, but nothing is filler.

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?

An output schema exists, so return values need not be explained, and the description correctly points the agent at the screen info in the response. The main residual gap is what happens on a blocked/denied transaction and how that surfaces to the caller.

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

Parameters1/5

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

Schema coverage is 0% for the single tcode parameter, so the description must carry full semantics — and it does: it names example tcodes (MM03, VA01, SM30) and the /n and /n/SCWM/MON formatting variants. This meaningfully exceeds the bare 'string' schema.

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 ('Execute (start/run) an SAP transaction code') and immediately disambiguates with concrete examples (MM03, VA01, SM30). It also clarifies the scope boundary — it navigates to the initial screen only, rather than performing the transaction's business logic.

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?

Gives explicit pre-call guidance: 'Use sap_get_session_info to see the current transaction before navigating away,' and warns about blocklist/allowlist constraints. It does not, however, distinguish this from siblings like sap_get_transaction_guide or explain when transaction navigation is preferable to direct screen-element interaction.

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