Skip to main content
Glama

inspect_element_responsiveness

Track a CSS-selected element across multiple viewports to see how its bounding box, font size, layout model, and padding scale.

Instructions

Track a specific element (e.g. hero section, nav bar, image, card grid, or button) across multiple viewports to analyze how its bounding box, font-size, layout model, and padding scale.

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": {
      "selector": "<selector>"
    },
    "name": "inspect_element_responsiveness"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS selector of the element to inspect
viewportsNoOptional list of viewports to test against

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 behavioral burden. It does disclose the measured properties (bounding box, font-size, layout model, padding), which implies a read-only inspection, but it omits what happens when the selector matches nothing, what viewports are used if the optional list is omitted, and whether the page must already be loaded.

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 front-loaded sentence with no filler, stating the action, the target, and the metrics. The parenthetical example list is slightly long but earns its place by disambiguating what counts as an 'element'.

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?

There is no output schema and no annotations, so the description must carry both behavioral and result context. It partially does so by naming the metrics that scale, but for a multi-viewport measurement tool it should also say how results are organized per viewport and what the default viewport set is.

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 coverage is 100%, so the schema already documents both parameters in detail, including viewport fields and ranges. The description reinforces the multi-viewport semantics of the optional list but adds no detail on default behavior when it is omitted or on accepted selector syntax, 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?

The description names a specific verb (track/analyze) and resource (a specific element identified by CSS selector) and enumerates concrete element types plus the metrics measured. It is clear what the tool does, but it never distinguishes itself from close siblings such as inspect_element or test_responsiveness, leaving the agent to infer that this is the element-level, multi-viewport variant.

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 'across multiple viewports' and the element examples, so an agent can infer the scenario (checking how one component scales). However, there is no explicit when-to-use statement, no mention of when to prefer a page-level responsiveness tool instead, and no stated prerequisites such as a page already being open.

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