Skip to main content
Glama

Sap Click Table Cell

sap_click_table_cell

Clicks a specific cell in an SAP ALV grid table, targeting the correct clickable element, to open detail views after reading table data. Supports single- or double-click actions.

Instructions

Click a cell in an ALV grid table. Automatically targets the correct clickable element (hotspot span vs TD). Use after sap_read_table to navigate to detail views.

Session parameter:

  • session=None (default): Uses primary session ("s1")

  • session="s2": Targets specific session (for parallel agents)

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

Input Schema

NameRequiredDescriptionDefault
rowYesRow number (1-indexed, data rows start at 1)
actionNo"click" for single click, "dblclick" for double-clickclick
columnYesColumn index (0-based) or column header name
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.

Output Schema

NameRequiredDescriptionDefault
rowYesRow that was clicked (1-indexed)
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
columnYesColumn that was clicked (index or header)
successNoWhether the operation succeeded
page_titleNoPage title after click
was_hotspotNoWhether cell was a navigation hotspot
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
selector_usedYesCSS selector that was used for the click

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add a useful behavioral detail — that it auto-resolves the clickable element type (hotspot span vs TD) — but it does not say what the click triggers (navigation, popup, selection), what happens if the cell is not clickable, or that a live logged-in session is required.

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?

The opening two sentences are front-loaded and precise. The multi-line session parameter block is somewhat redundant with the schema's own session description and could be trimmed, but it is not misleading or padded with filler.

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 values need not be explained, and the description covers purpose, sequencing, and session targeting. The main residual gap is failure/edge-case behavior for cells that are not clickable, which is minor for a focused click primitive.

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 coverage is 100%, so row indexing, column index-vs-header, and the click/dblclick action are already documented in the schema. The description's session block largely restates the schema's session description rather than adding new meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource — 'Click a cell in an ALV grid table' — and further distinguishes the target from generic clicking by noting it picks the right element ('hotspot span vs TD'). An agent can tell this apart from sap_click_button or browser_click without opening any schema.

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?

It states a clear usage context: 'Use after sap_read_table to navigate to detail views,' which establishes sequencing and intent. It does not, however, say when not to use it (e.g., non-ALV tables or when a button click is needed instead), so it falls short of full when/when-not guidance.

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