Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Select option

select

Choose one or more option values in a dropdown control, targeting by ref, CSS selector, text, or role+name for reliable form interaction.

Instructions

Choose one or more values in a select element. Target one of: ref (preferred), selector, text, or role+name.

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

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot, e.g. e12. Preferred over selectors.
nameNoAccessible name to combine with role.
roleNoARIA role, e.g. button, link, textbox, checkbox, combobox.
textNoVisible text to match (first match wins).
exactNoRequire exact text/name match.
valuesYesOption values or labels.
confirmNoConfirm a high-impact action when the server policy is ask.
observeNoReturn a compact change observation after the action (default true).
selectorNoCSS selector (use when no ref is available).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotation only says readOnlyHint=false, so the description carries the mutating-operation burden and does little with it: no mention of what happens if a value does not exist, whether it throws or silently skips, or whether it dispatches change events. It adds targeting semantics but discloses nothing about failure modes or side effects of the selection itself.

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 sentences, front-loaded with the action and then the targeting options, with no filler. The targeting preference is placed where an agent needs it before choosing parameters.

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 9-parameter mutating tool with no output schema, the description covers the riskiest decision, which locator to use, and the schema documents the rest in detail. What is still missing is behavior on unmatched values and whether multi-select or event dispatch is implied, which keeps it short of complete.

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?

The schema coverage is 100%, so the baseline is 3, and the description goes beyond the schema by framing ref, selector, text, and role+name as mutually exclusive targeting alternatives rather than independent optional fields. It does not add anything on values, exact, confirm, or observe, but the exclusivity framing is genuine added meaning.

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?

The description states a specific verb and resource: 'Choose one or more <option> values in a select element.' That is precise enough to separate it from fill/type/click without opening the schema, though it never says how it differs from those siblings in behavior.

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?

It gives one clear preference, 'ref (preferred)', over selector/text/role+name, which is real targeting guidance. But there is no when-not guidance: nothing says to use click/type for custom dropdowns or fill for text inputs, and no statement about prerequisites such as needing a fresh snapshot for ref.

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