Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Get Cell Info

sap_get_cell_info
Read-only

Retrieves detailed metadata from an ALV grid cell, including value, editability, cell type, validation state, F4 help, hotspot, color, and tooltip. Use it to inspect cells before reading or changing data.

Instructions

Get detailed cell metadata from an ALV grid.

Returns value, changeable, cell_type (Normal, CheckBox, ValueList, Button, ...), state (Normal, Error, Warning, Info: why a cell was rejected), f4_help, hotspot, color, tooltip, max_length; plus checked for a checkbox and list_box_count (entries) for a dropdown cell. Does NOT work on GuiTableControl.

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_get_cell_info"
  }
}

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the semantic meaning of the 'state' field (why a cell was rejected) and the hard limitation on GuiTableControl, which is behavioral and not derivable from schema or annotations.

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?

Front-loaded with purpose in the first sentence, then the field inventory, then the limitation last. The long parenthetical enumerations (cell_type, state) are dense but each item is an informative value domain rather than filler.

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?

A read-only tool with an output schema, so the return-value inventory is largely redundant and the description does not need to explain results. What it omits — parameter addressing conventions and how to obtain a valid grid_id — is the part an agent actually needs before calling.

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% for all three required parameters, so the description carries the full burden — yet it says nothing about grid_id format, whether row is zero- or one-based, or whether column is a name, index, or key. Only the return fields are described, leaving invocation details entirely to inference.

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?

Specific verb+resource ('Get detailed cell metadata from an ALV grid') with an enumerated payload and an explicit scope boundary ('Does NOT work on GuiTableControl'). An agent can distinguish it from sap_read_table, sap_get_column_info, and the GuiTableControl tools 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?

Provides a clear when-not condition (GuiTableControl unsupported), which is the single most likely misselection here. However, it never names the alternative for that case (e.g. sap_get_table_control_row_info) nor contrasts with siblings like sap_get_column_info or sap_get_current_cell.

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