MCP SAP GUI Server

Overview Schema Source Related Servers Discussions Admin

Sap Select Table Row

sap_select_table_row

Select a specific row in SAP GUI ALV grids or table controls using a zero-based index; automatically scrolls to make the row visible when needed.

Instructions

Select a row in a table/grid.

Works on both ALV grids and table controls. Row index is zero-based. For ALV: uses absolute row index. For TableControl: scrolls to make the row visible first if needed.

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": {
      "table_id": "<table_id>",
      "row": "<row>"
    },
    "name": "sap_select_table_row"
  }
}

Input Schema

Name	Required	Description	Default
`row`	Yes
`table_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, which is already informative. The description adds genuine behavioral detail beyond them: zero-based indexing, absolute indexing on ALV, and the side effect that TableControl scrolls the row into view. It omits whether selection replaces any prior selection and whether a failure/not-found condition is reported.

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?

Four short sentences, front-loaded with the core action, then the ALV/TableControl nuance. No filler; the only mild redundancy is naming both 'table' and 'grid'.

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

Completeness3/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 no explanation, and the tool is structurally simple with only two parameters. Still, the unidentified `table_id` and the lack of any note on selection semantics or error behaviour leave a gap an agent would hit on first call.

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 coverage is 0%, so the description carries the full burden. It explains the `row` parameter well (zero-based, absolute for ALV, auto-scrolled for TableControl) but never says what `table_id` is or where to obtain it, leaving a required identifier undocumented in both schema and description.

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 ('Select a row in a table/grid') and clarifies both supported surface types (ALV grid vs. table control). It doesn't explicitly mark the boundary against neighbours like sap_select_multiple_rows, sap_set_current_cell, or sap_select_all_rows, so twins remain distinguishable only by inference.

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 implied by the resource ('select a row'), and the ALV/TableControl split hints at when each behaviour applies. However, there is no explicit 'use this instead of X when...' guidance and no statement of prerequisites (e.g., that the table must already be read/visible before selecting).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server