MCP SAP GUI Server

Overview Schema Source Related Servers Discussions Admin

Sap Set Field

sap_set_field

Sets a value into an SAP GUI input field or dropdown on the current screen, selecting dropdown entries by key or text and rejecting invalid or non-editable fields.

Instructions

Set (type/enter) a value into an input field on the current SAP screen.

Works on GuiTextField and GuiCTextField input fields, and on dropdowns (GuiComboBox, ID prefix cmb): there value picks the entry by its key or its text, and the response reports the key and text selected. For filling in multiple fields of a form at once, use sap_set_batch_fields instead. After setting a field, you may need to press Enter to trigger validation.

A value longer than the field (MaxLength) or a field that is not changeable is refused before writing: status 'rejected' and an error that says which, and the field keeps its content.

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": {
      "field_id": "<field_id>",
      "value": "<value>"
    },
    "name": "sap_set_field"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes
`field_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

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses pre-write validation (MaxLength and non-changeable fields), the 'rejected' status, that an error names the cause, and that the field retains its content on refusal, plus what the response reports for dropdowns. That is meaningful mutation-safety context the readOnlyHint/destructiveHint flags do not convey.

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?

Three tight paragraphs, front-loaded with the core action, then element coverage and the sibling alternative, then failure semantics. No filler sentences.

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-value detail is appropriately omitted, and the writer discloses failure behavior for a mutation. The only gap is how to discover a valid field_id, which for a 2-required-param tool with no schema descriptions is a notable omission.

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 0%, so the description must carry both parameters. It does explain 'value' for dropdowns (key or text disambiguation) but says nothing about 'field_id' format or how to obtain one (e.g. via sap_get_screen_info / sap_get_screen_elements), leaving half the surface undocumented.

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?

States a specific verb and resource ('Set (type/enter) a value into an input field on the current SAP screen') and enumerates the exact element types it covers (GuiTextField, GuiCTextField, GuiComboBox). It also names the sibling (sap_set_batch_fields) it is not, so an agent can route correctly without opening a 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?

Explicitly routes multi-field form filling to sap_set_batch_fields and notes that Enter may be needed afterwards for validation. It does not, however, clarify when to prefer the sibling sap_select_combobox_entry over this tool for dropdowns, which is a real overlap left to inference.

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

Deploy Server