Skip to main content
Glama

Select options

browser_select
Idempotent

Select options in a native dropdown by label or value, replacing the current selection and returning the chosen values plus what changed.

Instructions

Choose options of a native by label or value, replacing the current selection (unlisted options are unselected). Custom dropdown: browser_click it, then the option. Returns the values selected and what changed.

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": {
      "ref": "<ref>",
      "values": "<values>"
    },
    "name": "browser_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesFrom the latest snapshot, e.g. "e12" or "f1e3"
valuesYesExact labels or values; several only for a multi-select

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / values / description
      Added value: +"Exact labels or values; several only for a multi-select"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world, so the safety envelope is covered. The description adds the non-obvious mutation semantics — the current selection is replaced and unlisted options become unselected — plus the return shape (selected values and what changed), which is real behavior beyond the structured fields. It stops short of stating permission/prerequisite needs or failure modes, keeping it at a 4.

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 sentences, front-loaded with the primary case, then the exception, then the result. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema mutation tool, everything needed to call it correctly is present: which element type, the label-vs-value input convention, the replacement behavior, and the fallback path for custom widgets.

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 100%, and the schema already says labels-or-values and multi-select-only-for-several. The description restates the same distinction without adding format details, ordering rules, or ambiguity resolution (e.g. label collides with a value). Baseline 3 is appropriate when the schema carries the parameter burden.

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?

"Choose options of a native <select> by label or value" names a specific verb, precise resource, and the addressing mechanism, then explicitly carves out the custom-dropdown case. The agent can distinguish this from browser_click without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: for native selects use this tool; for custom dropdowns, browser_click the control first and then the option. That is a when/when-not pair with a named alternative, not an inference.

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