Skip to main content
Glama
Sign In
MCP SAP GUI Server

MCP SAP GUI Server

by kts982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sap Select Combobox Entry

sap_select_combobox_entry

Selects a dropdown entry in SAP GUI by technical key or visible text, enabling accurate combobox value selection during automation.

Instructions

Select an entry in a combobox/dropdown by its key or display value text.

Accepts either the technical key or the visible display text. Use sap_get_combobox_entries first to see all valid options. F4 opens nothing on a dropdown; sap_set_field selects entries the same way.

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": {
      "combobox_id": "<combobox_id>",
      "key_or_value": "<key_or_value>"
    },
    "name": "sap_select_combobox_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
combobox_idYes
key_or_valueYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-destructive action, and the description adds useful behavior context: both key and display text are accepted, and F4 does not open dropdowns. It does not explain what happens on an invalid key/value, whether selection triggers downstream events, or whether the operation commits immediately.

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 core action is front-loaded in the first sentence, followed by concise clarifications. The F4 note is slightly cryptic but contextually useful; overall there is little waste.

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?

With only two parameters and an output schema available, the description covers the critical input semantics and the prerequisite discovery step. What remains missing — error behavior and post-selection side effects — is secondary given the output schema and annotations.

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 that key_or_value accepts either the technical key or visible display text, which adds real meaning beyond the schema, but combobox_id is left 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 — selecting an entry in a combobox/dropdown — and clarifies the two accepted identifier forms. It also names the sibling to consult first and the sibling that can do the same job, so the agent can distinguish it from adjacent tools.

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 instructs the agent to call sap_get_combobox_entries first and notes that sap_set_field selects entries the same way, which gives a clear alternative path. It lacks an explicit 'when not to use' rule, but the prerequisite guidance is strong.

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