Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Set Current Cell

sap_set_current_cell

Sets the focused cell in an ALV grid or table control so toolbar actions target the intended row and column. Use before pressing cell-dependent toolbar buttons.

Instructions

Set the current (focused) cell in an ALV grid or table control.

Useful before pressing toolbar buttons that act on the current cell.

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>",
      "row": "<row>",
      "column": "<column>"
    },
    "name": "sap_set_current_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowYes
columnYes
grid_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already indicate this is not read-only but is non-destructive, and the description adds that the operation sets UI focus/current cell rather than changing data. It still does not explain side effects, whether a prior selection is replaced, or whether the focus change affects subsequent toolbar actions beyond the brief hint.

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, front-loaded with the core action and followed by a useful context note. There is no redundant or filler text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 described. However, for a tool with three required, undocumented parameters, the description is incomplete: it gives purpose and one usage hint but does not compensate for the 0% schema description coverage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It implies that grid_id, row, and column identify a cell in an ALV grid or table control, but it never explains row indexing, column format, or how grid_id should be obtained.

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 states a specific verb and resource: set the current focused cell in an ALV grid or table control. It is clearer than the title alone and distinguishes the action from data-modifying siblings, but it does not explicitly differentiate from nearby tools such as sap_set_focus or sap_select_table_row.

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?

It gives one clear usage context: before pressing toolbar buttons that act on the current cell. However, it does not say when not to use it or how it differs from related focus/selection tools like sap_set_focus or sap_select_table_row.

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