Skip to main content
Glama
Sign In
vibatchium

vibatchium

by trueoriginlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

select

Pick an option by value, label, or index; for custom dropdowns, pass the opener button and option label.

Instructions

Pick an option on a by value/label/index. Also works on a custom dropdown: pass the button that opens it and the option's label.

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": {
      "target": "<target>"
    },
    "name": "select"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoZero-based option index.
labelNoOption visible label.
leaseNoOptional lease token to present if the target session is leased (0.7.0). Threaded per-call; never read from the server's env.
valueNoOption value attribute.
targetYes@eN or selector for the <select>.
sessionNoOptional session name to target (omit for the shared 'default'). On a daemon shared with other agents, pass a UNIQUE name for stateful multi-step work (go→click→fill) so you don't collide on 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 full disclosure burden. It usefully reveals the custom-dropdown open-then-pick behavior, which the agent could not infer otherwise, but says nothing about whether change/input events are dispatched (critical for controlled widgets), whether it waits for options to populate, or what happens when a matching option is absent.

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?

Two tight sentences with the core action front-loaded and the exception case placed after it. No filler, no restatement of the tool name, and every clause carries information an agent needs.

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?

With 6 parameters, full schema coverage, and no output schema, the definition only needs to cover purpose and the tricky invocation path, which it largely does. It is still thin on error behavior, option precedence, and whether hidden/disabled options are selectable — gaps that matter for a state-mutating UI action with no annotations to fall back on.

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 100%, so the baseline is 3, but the description adds genuine meaning: it clarifies that target is not only the <select> itself but may be the button that opens a custom dropdown, and that label is the required key in that path. That refines the schema's narrower wording ("@eN or selector for the <select>") rather than repeating it.

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 and resource ("Pick an option on a <select>") plus the three selection keys, which clearly separates it from generic interaction siblings like click, fill, or type. It does not explicitly name when a sibling such as click or type would be the wrong choice, so it stops short of a 5.

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?

Gives concrete guidance for the non-obvious case ("Also works on a custom dropdown: pass the button that opens it and the option's label"), which is real when-to-use help. It never says whether value/label/index are mutually exclusive or which wins if several are supplied, and never excludes using it on non-option elements, leaving the primary path implied.

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