select_option
Select an option from a dropdown list by its value or label in a live Firefox browser session.
Instructions
Select an in a by value or label.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | ||
| selector | Yes |
Select an option from a dropdown list by its value or label in a live Firefox browser session.
Select an in a by value or label.
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | ||
| selector | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description does not disclose whether the tool clears previous selection, waits for options to be enabled, or handles dynamic dropdowns.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with key action. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Minimal information for a form interaction tool. No mention of return values, error states, or handling of non-existent options. With no annotations or output schema, more context is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%. Description implies 'value' can accept either value or label, but does not clarify which parameter maps to which. No explanation of 'selector' (e.g., CSS selector or XPath).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Select'), the target ('<option> in a <select>'), and the method ('by value or label'). It distinguishes itself from sibling tools like 'click' or 'type_text'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'click' or 'type_text'. No context about prerequisites or fallback options.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sinamohsenifar/foxbridge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server