chromaphore-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Pick in a dropdown

select

Picks options in a dropdown or multiple-choice list by visible text or value, opening the list or using keys when it cannot open, and rejecting invalid values.

Instructions

Picks options in a the way a person does (opens its list and clicks, or uses the keys when the list cannot open). values: one for a dropdown, the exact set for a multiple list; each matches an option by its visible text or its value. A wrong value is refused with the options there are.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	An element id from a listing, such as a12.
`values`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description usefully discloses how selection happens: opening the list and clicking like a person, falling back to keyboard use when the list cannot open. It also explains matching by visible text or value and that invalid values are refused with available options, though it omits details like waiting behavior and exact error/return mechanics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the core action, with parameter semantics and failure behavior following in sequence. Minor awkward phrasing such as 'with the options there are' does not seriously hurt readability.

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 selection tool with no output schema or annotations, the description covers the important behavior: interaction mode, value matching, single vs multiple semantics, and invalid-value handling. Some edge-case behavior remains unspecified, but the core calling information is present.

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 only 50%, with id documented but values not meaningfully described. The description compensates by explaining that values must contain one option for a dropdown or the exact set for a multiple list, and that each value matches an option by visible text or value.

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 action and resource: picking options in a <select> element, including both single dropdown and multiple-list behavior. This distinguishes it from generic click/type tools and from tab_select, though it does not explicitly name alternatives.

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?

Usage is implied by the <select> scope and by the values semantics for single vs multiple lists. However, it does not explicitly say when to prefer this over click, type, or tab_select, nor does it state exclusions or prerequisites.

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

Deploy Server