Skip to main content
Glama

Sap Set Radio Button

sap_set_radio_button

Selects a SAP radio button by its label text, letting agents set form options in desktop GUI or WebGUI sessions. Use sap_get_form_fields first to view available radio buttons and current selection.

Instructions

Select a SAP radio button by its label text.

Use sap_get_form_fields first to see available radio buttons and which is selected.

Args:

  • label: Radio button label text (e.g., 'Datenbanktabelle', 'Database table')

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>"
    },
    "name": "sap_set_radio_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes
sessionNo
agent_idNo

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
labelNoLabel or selector used to find the field
popupNoPresent when a popup dialog is active on screen
valueNoValue that was set
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.
selector_usedNoCSS selector that matched the field
available_optionsNoFor dropdown fields: list of valid options when requested value was not found

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 behavioral burden. It usefully discloses session targeting semantics and the discovery prerequisite, but says nothing about failure behavior for an unknown/ambiguous label, whether the selection fires screen events or triggers a round trip, or whether the action is idempotent. Return values are covered by the output schema, so that omission is acceptable.

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-loads the purpose in the first sentence, then the prerequisite, then argument notes. The bilingual label examples add real value rather than padding. The 'Session parameter' block is slightly verbose for what it says, but nothing is wasteful.

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?

Return values are handled by the output schema, and the core action plus its prerequisite are covered. The unexplained 'agent_id' parameter and the absence of any error or side-effect guidance leave meaningful gaps for a UI-mutating tool with zero annotation coverage.

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 well for 'label' (concrete SAP examples: 'Datenbanktabelle', 'Database table') and for 'session' (default primary 's1' vs. explicit 's2'). However, the third parameter 'agent_id' is never mentioned anywhere, leaving one of three parameters entirely 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?

Names a specific verb and resource ('Select a SAP radio button') plus the selector mechanism ('by its label text'), which cleanly separates it from siblings like sap_set_checkbox, sap_click_button, and sap_set_field. An agent can pick this tool from the name-plus-description alone.

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 prescribes a prerequisite workflow: 'Use sap_get_form_fields first to see available radio buttons and which is selected.' That tells the agent both how to discover valid labels and how to check current state before acting. It stops short of stating when NOT to use it (e.g., for checkboxes or buttons), but those have distinct sibling names.

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