Skip to main content
Glama

inspect_ancestors

Identify the ancestor that constrains an element's width, height, position, overflow, or stacking. Resolve layout issues where the cause is above the element.

Instructions

Walk an element's ancestor chain for ONE concern — width, height, position, overflow, or stacking — and flag the ancestor that is the binding constraint. Use when the cause lives ABOVE the element: it's too wide/narrow, clipped or cut off, won't scroll, is mysteriously positioned, or a z-index has no effect (trapped in an ancestor's stacking context). Complements explain_styles, which explains the element's own winning rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoViewport x coordinate (use with y)
yNoViewport y coordinate (use with x)
uidNoElement uid from a prior page_snapshot (e.g. "e8")
concernNoWhich constraint chain to report (default: width)
selectorNoCSS selector — first match is used
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the tool analyzes one concern per call and flags the binding constraint. While it doesn't mention side effects or auth needs, as a read-only analysis tool, the behavioral description is sufficient and accurate.

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?

The description is two sentences plus a usage sentence, all front-loaded and each adding value. No redundant phrases, and information is prioritized clearly.

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

Completeness5/5

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

Given 5 parameters, full schema coverage, no output schema, and complexity of ancestor analysis, the description covers purpose, usage, and relation to siblings. It is complete for a read-only analysis tool.

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 baseline is 3. The description adds minimal new parameter info beyond what schema provides, but it frames the overall flow (walk ancestor chain for one concern) which adds context. No additional parameter details are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool walks an element's ancestor chain for one concern (width, height, position, overflow, or stacking) and flags the binding constraint. It uses specific verbs like 'walk' and 'flag' and distinguishes itself from sibling 'explain_styles'.

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

Usage Guidelines4/5

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

The description explicitly lists when to use: when cause lives above the element (too wide/narrow, clipped, won't scroll, mysteriously positioned, or z-index ineffective). It mentions complementing 'explain_styles' but does not explicitly state when not to use, though the positive guidance is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mi60dev/visionaire-engine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server