Skip to main content
Glama
Sign In
android-layout-inspector-mcp

android-layout-inspector-mcp

by Rixmerz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Element Context

element_context

Inspect a selected UI element's geometry, ancestry, siblings, and collisions to identify layout issues like overlaps or clipping. Choose the element by resource-id or text.

Instructions

Deep dive on one node: its geometry, ancestry, siblings and collisions.

selector matches a resource-id, then exact text, then a substring of text or content-desc.

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": "element_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
selectorYes
xml_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 adds useful behavioral detail about selector resolution order, but does not explicitly disclose whether the operation is read-only or whether any permissions are required. For an inspection tool this is a moderate gap, not a severe one.

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 sentences, no filler, and the main purpose is front-loaded. The selector-resolution sentence earns its place and is directly actionable for an agent.

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?

The output schema exists, so return values are covered externally, and the primary required parameter is well documented. Missing pieces include optional parameter meanings and an explicit statement about side effects or read-only behavior, leaving the definition adequate but not fully complete.

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?

The required `selector` parameter is well explained with the matching order (resource-id, exact text, then substring of text/content-desc). However, schema description coverage is 0% and the optional `device` and `xml_path` parameters are left completely unexplained, so the description only partially compensates.

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 clearly states the tool's focus: 'Deep dive on one node' and lists the outputs it provides (geometry, ancestry, siblings, collisions). It distinguishes from layout-wide siblings like inspect_layout by emphasizing a single node, but does not explicitly name a sibling alternative.

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 selector matching precedence is clearly specified, which tells the agent exactly how to target a node. 'Deep dive on one node' provides clear context for when to use the tool, though it does not explicitly state when not to use it or which sibling tool to prefer.

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

Deploy Server

Other Tools