Skip to main content
Glama

app_layout

Retrieves element positions, window coordinates, and font sizes from the current screen to verify layouts and support visual adjustments; use app_snapshot instead for cheaper UI actions.

Instructions

Positions (dp, window coordinates) and font sizes of elements on the current screen. For layout checks and visual work; app_snapshot is cheaper for acting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "app_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax elements, default 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 does disclose a relative cost trait (app_snapshot is cheaper) and the coordinate units, which are genuinely useful. However it says nothing about whether results are truncated at the default 250 elements, how entries are ordered, or whether each entry identifies its element, so an agent cannot predict what it will actually receive.

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 with zero filler: the returned data and units come first, then the usage guidance and the cheaper alternative. Every clause earns its place.

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, so the description must convey the shape of the response, and it only partially does: it names positions and font sizes but not the entry structure, element identification, or ordering. For a read tool that returns bulk geometry (up to 250 elements) this leaves a meaningful gap.

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% for the single 'limit' parameter, so the schema already documents the default of 250 elements. The description adds nothing about the parameter, and does not warn about truncation when the cap is hit, so the baseline of 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 the exact data returned (element positions and font sizes on the current screen) with units (dp, window coordinates), which is enough to distinguish it from siblings. It stops short of a clear action verb, reading more like an output summary than 'return the layout geometry', but the resource and scope are unambiguous.

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

Usage Guidelines5/5

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

It states the intended use case ('layout checks and visual work') and explicitly routes the agent elsewhere when the goal is interaction, naming app_snapshot as the cheaper alternative. That is the when-to-use / when-to-prefer-a-sibling pair an agent needs.

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