Skip to main content
Glama

select_option

Choose one or more options in a select element by label or value to set form fields and trigger dependent UI updates.

Instructions

Choose one or more options in a select element, by label or value.

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": "select_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesElement ref from the latest snapshot, e.g. "e14".
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 and largely doesn't. It never says whether a selection replaces or appends to existing selections in a multi-select, whether change/input events are dispatched, or what happens if ref points to a non-select element. The only behavioral hint is 'one or more options', which implies multi-select support.

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?

One short sentence, front-loaded with the action and resource, with zero filler. Its brevity is close to under-specification rather than bloat, so it is efficient but not maximally informative.

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

Completeness2/5

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

For a mutation-style interaction tool with no annotations and no output schema, the description omits the details an agent most needs: replace-vs-append semantics, event dispatch, and failure modes on mismatched refs or labels. What remains is a correct but thin one-liner.

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 coverage is 67% and the undocumented parameter is exactly the one the description rescues: 'by label or value' tells the agent what strings the values array accepts, which the schema leaves bare. It does not clarify ordering/precedence when both a label and a value could match, but it meaningfully compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('choose') and resource ('options in a select element') plus the addressing mode ('by label or value'), which is enough to distinguish it from click/fill_form. It stops short of explicitly naming a sibling it replaces or is replaced by.

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

Usage Guidelines3/5

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

Usage is only implied by the resource type: an agent can infer it should be used for <select> elements rather than text inputs or buttons. There is no explicit when-to-use/when-not guidance and no named alternative for multi-select widgets or custom dropdowns that are not real select elements.

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