Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Press Alv Toolbar Button

sap_press_alv_toolbar_button

Activates a toolbar button on an SAP ALV grid to perform actions such as sorting, filtering, or exporting; retrieve valid button IDs with the ALV toolbar lookup first.

Instructions

Press a toolbar button on an ALV grid (e.g., sort, filter, export).

Use sap_get_alv_toolbar to find button IDs. A menu button (Menu / ButtonAndMenu) opens its menu and the response lists menu_items (text and function_code); pick one with sap_select_alv_context_menu_item.

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": {
      "grid_id": "<grid_id>",
      "button_id": "<button_id>"
    },
    "name": "sap_press_alv_toolbar_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
grid_idYes
button_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds genuinely new behavior: menu-type buttons open a menu and the response carries menu_items with text and function_code. That is real response-shape information beyond the annotations. It stops short of saying what a normal push does to the screen or whether popups/dialogs can result.

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 short sentences, purpose first, procedural detail second; every clause carries information and nothing is padded.

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?

With an output schema present, return values need no explanation, and the menu_items behavior plus the discovery workflow cover the main risks. The unresolved grid_id semantics is the one real hole for a 2-parameter tool.

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 0% for both parameters, so the description must compensate. It does explain where button_id comes from (sap_get_alv_toolbar), but grid_id is never mentioned or explained, leaving one of two parameters undocumented in both places.

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 concrete verb+resource scoped to ALV grids, with examples (sort, filter, export) that make the target obvious. The ALV qualifier separates it from the generic sap_press_button, though it never names that sibling directly.

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 an explicit prerequisite workflow: use sap_get_alv_toolbar to obtain button IDs. Also handles the branch case — Menu/ButtonAndMenu buttons open a menu and the follow-up is sap_select_alv_context_menu_item — so the agent knows what to do next. Missing only an explicit exclusion (e.g., non-ALV buttons belong to another tool).

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