Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_fill_or_select

Fills a form element or selects an option with a specified value using a CSS selector in a DICloak browser environment.

Instructions

Fill a form element or select an option with the specified value

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": {
      "envId": "<envId>",
      "selector": "<selector>",
      "value": "<value>"
    },
    "name": "chrome_fill_or_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.
valueYesValue to fill or select into the element
selectorYesCSS selector for the input element to fill or select

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether filling dispatches input/change events, whether it replaces or appends to existing content, whether it focuses the element, whether select matches by value or label, or whether it waits for the element to appear.

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?

It is a single tightly worded sentence with no filler and the action is front-loaded. Brevity here is achieved by omission rather than by disciplined compression, but structurally nothing is wasted.

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

Completeness3/5

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

With three required parameters fully documented and no output schema, the schema covers the calling contract. However, for a mutation tool with zero annotations, the description leaves out the effects, event behavior, and failure semantics an agent would need to use it reliably.

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 description coverage is 100%, so envId, selector, and value are already documented in the input schema. The description restates the value/selector relationship ("specified value") without adding syntax, format, or edge-case meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb pair and resource: "Fill a form element or select an option with the specified value." An agent can tell it mutates a form control rather than clicking or typing keys. It does not differentiate from near-siblings such as chrome_click_element or chrome_keyboard, which is why it falls short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to reach for this tool versus chrome_click_element or chrome_keyboard, no preconditions (element must exist/be visible), and no note on what to do on failure. The agent must infer usage entirely from the name.

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