Skip to main content
Glama

Sap Select Dropdown

sap_select_dropdown

Select a specific dropdown or combobox value on the current SAP screen by field label and exact option text; on failure, returns available options to correct the selection.

Instructions

Select a value from a dropdown (combobox) field on the current SAP screen.

Use sap_get_form_fields(include_dropdown_options=True) first to see available dropdown fields and their options.

Unlike sap_set_field which auto-detects field type, this tool is specifically for dropdown selection and returns available_options on failure.

Args:

  • label: Dropdown field label text (e.g., 'Country', 'Language', 'Buchungskreis')

  • value: Exact option text to select from the dropdown

Session parameter:

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

  • session="s2": Targets specific session

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": {
      "label": "<label>",
      "value": "<value>"
    },
    "name": "sap_select_dropdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes
valueYes
sessionNo
agent_idNo

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
labelYesDropdown field label
popupNoPresent when a popup dialog is active on screen
valueYesOption value that was selected
successNoWhether the operation succeeded
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
available_optionsNoAvailable options if selection failed (e.g., value not found)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and openWorldHint=false, so the safety profile is partially covered. The description adds useful behavior beyond annotations: it returns available_options on failure and explains that session defaults to primary session 's1' while session='s2' targets a specific session.

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?

The description is front-loaded with purpose and prerequisite guidance, then uses compact argument bullets. Every sentence adds useful information, and there is no obvious repetition or 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?

The tool has an output schema, so the description need not explain return values generally. It still helpfully notes the failure behavior of returning available_options and covers the dropdown-specific prerequisite. It is nearly complete, though it could say more about session prerequisites or side effects for this mutating UI interaction.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 carry the burden of explaining parameters. It explains label with concrete examples such as 'Country', 'Language', and 'Buchungskreis', explains value as exact option text, and explains session behavior. It does not explain the agent_id parameter, which is the main remaining gap.

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 states a specific verb and resource: select a value from a dropdown/combobox field on the current SAP screen. It also distinguishes this tool from the sibling sap_set_field by explaining that sap_set_field auto-detects field type while this tool is specifically for dropdown selection.

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?

The description gives clear usage guidance: call sap_get_form_fields(include_dropdown_options=True) first to see available dropdown fields and options. It also names the alternative sap_set_field and explains the distinction. It does not explicitly state when not to use this tool, but the dropdown-specific scope makes the boundary reasonably clear.

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