Skip to main content
Glama

Browser Select Option

browser_select_option

Select an option from a dropdown/select element by CSS selector and value or label; supports session targeting for parallel SAP GUI agents.

Instructions

Select an option from a dropdown/select element. For SAP dropdowns, prefer sap_fill_form or sap_set_field which handle SAP-specific dropdown behavior. Args: selector = CSS selector for select element, value = option value to select, label = option text (alternative to value).

Session parameter:

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

  • session="s2": Targets specific session (for parallel agents)

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": {
      "selector": "<selector>"
    },
    "name": "browser_select_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOption text (alternative to value).
valueNoOption value to select.
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
selectorYesCSS selector for the select element.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
selectorYesSelect element selector
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
selected_labelNoLabel selected
selected_valueNoValue selected

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses session targeting semantics (primary session vs explicit 's2' for parallel agents), which is genuine added context, but it says nothing about failure modes (option not found, element not yet present), waiting behavior, or whether the selection fires change events. That leaves notable gaps for a DOM-mutating tool.

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 core action in one sentence, then the SAP routing, then session semantics as a clearly delimited block. The inline 'Args:' enumeration largely duplicates the schema and is the main wasted content.

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 values need not be explained, and parameter documentation is fully covered. What remains unaddressed is whether at least one of value/label is required (only selector is required), which is the main ambiguity an agent would hit when calling it.

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 100%, so all five parameters are already documented in the schema, establishing the baseline of 3. The description restates selector/value/label meaning and adds only marginal value on session (the 'parallel agents' rationale); it never mentions the agent_id parameter at all.

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 ('Select an option from a dropdown/select element') and immediately distinguishes itself from SAP dropdown siblings by naming sap_fill_form and sap_set_field as the preferred path for those cases. An agent can tell what this does and what it is not for without opening the 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?

Gives explicit conditional routing: for SAP dropdowns use sap_fill_form or sap_set_field instead. It does not cover the choice between passing 'value' vs 'label', nor when a plain browser_click would be preferable, but the primary exclusion is stated clearly.

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