Skip to main content
Glama

app_snapshot

Capture a compact text outline of the current app screen with actionable [refs] for buttons, inputs, text, and lists. Use it instead of screenshots to see and act on UI state.

Instructions

Compact text outline of the current screen (buttons, inputs, text, lists) with refs like [e3] to act on. Prefer this over screenshots.

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_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxLinesNodefault 400

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does imply a non-destructive read by describing a screen outline whose refs are meant for later actions. It does not state whether refs stay valid across screen changes, whether the call blocks until the UI settles, or what happens if no screen is loaded — relevant gaps for an agent sequencing tap/type calls.

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 tight sentences: the output format and ref convention come first, the preference over screenshots second. Nothing is wasted and nothing is buried.

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?

For a one-optional-parameter read tool with no output schema, the description covers what the agent needs to know: it returns text with actionable refs. The missing piece is guidance on ref lifecycle and staleness after UI changes, which matters given there are tap/type siblings acting on those refs.

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 single optional maxLines parameter is fully documented in the schema (default 400, integer), so the schema already does the explaining. The description adds no meaning about how truncation affects ref availability, which is the one semantic detail that would have added value.

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 resource precisely — a compact text outline of the current screen — and enumerates its contents (buttons, inputs, text, lists) plus the [e3] ref format used for subsequent actions. That is enough to separate it from sibling tools like app_screenshot or app_layout, though it opens with a noun phrase rather than an explicit verb.

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?

"Prefer this over screenshots" gives an explicit selection rule against the obvious alternative (app_screenshot). It offers no exclusions for when a screenshot or another inspection tool would be preferable, so the guidance is clear but one-sided.

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