Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Get Workflow Guide

sap_get_workflow_guide
Read-only

Get step-by-step guidance for SAP workflows like F4 search help, table export, and SPRO customizing navigation.

Instructions

Return step-by-step guidance for a common SAP workflow.

Available workflows:

  • search_help: F4 search help on a field. target = field ID.

  • table_export: Paginated table export. target = table element ID.

  • spro_navigate: SPRO customizing navigation. target = activity name.

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": {
      "workflow": "<workflow>",
      "target": "<target>"
    },
    "name": "sap_get_workflow_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
workflowYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the output is guidance rather than an action, but says nothing about connection prerequisites or whether the guide is static vs. screen-dependent — context that matters in this automation toolset.

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?

One framing sentence followed by a scannable bullet list where each entry pairs the workflow name with its target semantics. No filler, and the purpose is front-loaded before the enumeration.

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-value documentation is unnecessary, and enum-to-parameter mapping is fully covered. What's left thin is the usage/routing context relative to the many sibling guide and execution tools.

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?

Schema description coverage is 0%, so the description has to carry the load, and it does: each enum value is named, and `target`'s meaning is spelled out per workflow (field ID, table element ID, activity name). Only minor gap is that valid `target` formats/naming conventions aren't illustrated.

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: 'Return step-by-step guidance for a common SAP workflow', then enumerates the three supported workflows. The agent knows exactly what comes back, though it isn't explicitly contrasted with the similarly-purposed sibling sap_get_transaction_guide.

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?

The bullet list implies these are workflows you'd invoke before performing them, but there is no explicit when-to-use statement, no when-not, and no routing guidance versus sap_get_transaction_guide. The agent must infer that this is a preparatory, documentation-lookup call.

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