Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_get_element_attributes

Retrieve all attributes of a page element by CSS selector, including computed styles, outerHTML, and bounding box, to inspect or debug its rendered state.

Instructions

Get all attributes of a specified element by CSS selector on the current page, including computed style, outerHTML, and bounding box.

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

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.
selectorYesCSS selector for the element to get attributes from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, and it does disclose the returned payload (attributes, computed style, outerHTML, bounding box), which implies a read-only operation. It says nothing about what happens when the selector matches nothing or multiple elements, nor about any permissions or context requirements, leaving meaningful behavioral gaps.

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 the verb and target first and the return payload appended. Every clause carries information, though the trailing list of returned fields could arguably be trimmed given it is not a formal output contract.

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?

There is no output schema, so the description takes on the job of describing return values and does so reasonably (attributes, computed style, outerHTML, bounding box). For a two-parameter read tool this is close to sufficient; only error and match-cardinality behavior is absent.

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 both envId and selector are already documented; the description only restates that the selector resolves to an element on the current page. It adds no detail about selector syntax, uniqueness expectations, or scoping beyond what the schema provides.

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 all attributes of a specified element by CSS selector') and names the data returned, which separates it from listing tools like chrome_get_interactive_elements and chrome_get_web_content. It stops short of explicitly naming a sibling it is not, so it is clear but not fully differentiated.

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 only implied: 'on the current page' signals inspection of an already-rendered element, and the selector requirement implies a known target. There is no statement about when to prefer this over chrome_get_web_content or chrome_get_interactive_elements, and no exclusion of cases such as elements not yet present.

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