Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Select Option

select_option

Set an HTML element's value and trigger change/input events for reliable form automation. Use aria_click for custom dropdowns.

Instructions

Set HTML .value + change/input events. For custom dropdowns use aria_click.

Ex: select_option('t0', '#country', 'BR') → {"ok":true}

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": {
      "tab_id": "<tab_id>",
      "selector": "<selector>",
      "value": "<value>"
    },
    "name": "select_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
tab_idYes
selectorYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that it sets .value and dispatches change/input events, plus an example return value, but does not describe failure modes, whether the option must exist, or other runtime constraints.

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 compact and front-loaded, with the core action first, the alternative second, and a short example last. Every sentence contributes useful information without waste.

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?

The purpose, event behavior, sibling alternative, and example return are covered, and an output schema exists. However, with zero parameter descriptions and no annotations, the definition remains incomplete about parameter semantics and edge-case behavior.

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

Parameters2/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. The example maps the three positional arguments and implies tab_id, selector, and value, but it does not explicitly define their meaning or formats, leaving meaningful gaps.

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: set an HTML <select> value and fire change/input events. It also explicitly distinguishes this from custom dropdown handling by directing custom dropdowns to aria_click, so an agent can tell the tool apart from the sibling alternative.

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 clearly indicates this tool is for native HTML <select> elements and names the alternative, aria_click, for custom dropdowns. That gives both a when-to-use condition and an explicit when-not condition.

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

Deploy Server

Other Tools