Skip to main content
Glama
beSaif

zenpilot

by beSaif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

select

Choose an option from a dropdown, combobox, or listbox by reference; filter when needed, click the matching option, and verify the page change.

Instructions

Choose an option in a dropdown (by ref): a , a combobox or a listbox.

Opens it, types to filter if it's a text field, clicks the option whose text is option
(or the only one starting with or containing it), then checks the choice took. Reports
what changed on the page, like click.

Input Schema

NameRequiredDescriptionDefault
refYes
optionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the open/filter/click/verify sequence and the option-matching heuristic. It omits what happens on no match, errors, or whether the operation is reversible.

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?

Front-loaded with the purpose, then efficiently details behavior and outcome. Every sentence adds useful information with no wasted wording.

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?

For a two-parameter action with no output schema or annotations, the description is nearly complete: it covers the selection flow, matching semantics, verification, and page-change reporting. Missing failure-mode behavior and ref sourcing are the main remaining gaps.

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 0%, so the description must compensate. It explains option matching well (exact text, or the only one starting with or containing it) but only says 'by ref' for ref, without defining its format or how to obtain it.

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: choose an option in a dropdown/select/combobox/listbox. The behavior is clearly distinct from generic click/type siblings because it explains opening, filtering, selecting, and verifying the choice.

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 clear context for when to use it: any dropdown, combobox, or listbox selection, with matching behavior described. It does not explicitly say when to use click or type instead, so it falls short of full alternative routing.

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