Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_get_interactive_elements

Retrieves interactive elements from the current browser page, optionally filtered by CSS selector, text, or element type, to support automated browser interaction and inspection.

Instructions

Get interactive elements from the current page. Returns a list of elements with their properties, if the list is empty, that means the tool failed to find any interactive elements.

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>"
    },
    "name": "chrome_get_interactive_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.
selectorNoCSS selector to filter interactive elements. Takes precedence over textQuery if both are provided.
textQueryNoText to search for within interactive elements (fuzzy search)
elementTypeNoType of interactive elements to retrieve (e.g. button, link, input)all
includeCoordinatesNoInclude element coordinates in the response (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that an empty list signals a tool failure rather than a legitimately empty page, which is a non-obvious behavioral trait. However, it says nothing about whether a browser session must be open, whether the page must be loaded, whether coordinates are included by default, or what happens when the page has not finished rendering.

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 short sentences, front-loaded with the core action, and the second sentence carries a genuinely useful failure signal rather than restating the name. Nothing superfluous.

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?

No annotations and no output schema, so the description is the only place to explain return values, yet 'a list of elements with their properties' is vague about what properties (text, selector, tag, coordinates) come back. For a 5-parameter inspection tool it covers the essentials but leaves the response shape underspecified.

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 the schema already documents envId, selector, textQuery, elementType, and includeCoordinates, including the selector-precedence rule. The description adds no extra meaning about how filtering combines or what the defaults imply, so baseline 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?

States a specific verb and resource ('Get interactive elements') scoped to 'the current page', so an agent knows exactly what it returns. It does not differentiate itself from siblings such as chrome_get_element_attributes or chrome_get_web_content, leaving the agent to guess which retrieval tool applies.

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?

No guidance on when to use this versus alternatives, no prerequisites (active session, page loaded), and no exclusions. The only conditional statement concerns empty results, not tool selection.

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