Skip to main content
Glama
Sign In
mmjb-mcp

mmjb-mcp

by foklepoint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

select

Choose a dropdown option by index from the last look() list to set a value during browser automation.

Instructions

Choose an option in the dropdown with this index, using the numbers from the last look().

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

Input Schema

NameRequiredDescriptionDefault
indexYes
optionYes
allow_writesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says nothing about whether selecting triggers navigation, what happens on failure, whether a browser must be attached, or how the allow_writes flag affects behavior — a notable gap for a mutation-style interaction tool.

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?

A single front-loaded sentence with no filler. The only cost is the ambiguity of "with this index", which slightly undercuts the otherwise efficient phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 3-parameter interactive tool with no annotations, no output schema, and 0% schema coverage needs the description to do more. It omits the option format, the allow_writes semantics, and the post-selection behavior, leaving real gaps for an agent to fill by guesswork.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with 3 parameters. The description partially explains index by tying it to "the numbers from the last look()", but the option parameter's expected format and the allow_writes flag (default false, potentially gating the write) are entirely undocumented in both schema and description.

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: "Choose an option in the dropdown with this index." This distinguishes it from most siblings like click and type, though it does not explicitly say why to prefer it over click for a dropdown. The phrase "with this index" is slightly ambiguous (dropdown index vs. option index) but recoverable.

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?

Provides a sequencing prerequisite — use the numbers from the last look() — which implies the tool must be called after a look(). However, it names no alternative or exclusion, so an agent gets an implied workflow rather than explicit when/when-not guidance.

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