Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Select Multiple Rows

sap_select_multiple_rows

Select multiple rows in an ALV grid or table control by passing a list of row indices for batch selection.

Instructions

Select multiple rows at once in an ALV grid or table control.

Pass a list of row indices (e.g., [0, 2, 5]).

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>",
      "rows": "<rows>"
    },
    "name": "sap_select_multiple_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
table_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this mutates UI selection state non-destructively. The description adds nothing beyond that: it doesn't say whether the new indices replace or extend the current selection, what happens with out-of-range indices, or whether the grid must already be focused/visible.

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, the action and target are front-loaded, and the second sentence gives the concrete argument shape. Nothing extraneous.

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 not be described. But for a 2-required-parameter UI mutation tool, the definition leaves table_id semantics, selection-replacement behavior, and index-base ambiguity unresolved — enough gaps that an agent could call it wrongly.

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%, so the description must compensate. It does explain 'rows' as a list of row indices with an example ([0, 2, 5]), hinting at 0-based indexing, but it says nothing about 'table_id' — what identifier format is expected or how to obtain it (sap_get_screen_info / sap_read_table).

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+resource ('Select multiple rows') and scopes it to an ALV grid or table control, which distinguishes it from generic table reading tools. However it never explicitly contrasts with the close siblings sap_select_table_row (single row) and sap_select_all_rows, so the agent must infer the boundary itself.

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 phrase 'multiple rows at once' implies the batch use case, but no explicit when-to-use/when-not or alternative routing (e.g., use sap_select_all_rows for everything, sap_select_table_row for one) is given. Usage is inferable but not stated.

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