Swipium

Overview Schema Source Related Servers Discussions Admin

Snapshot the screen

qa_snapshot

Read-only

Read the current mobile screen as interactive, addressable @e1-style element refs with a snapshotQuality verdict so agents can target qa_act actions; call before acting and after navigation.

Instructions

Read the current screen as addressable elements (@e1, @e2...) for qa_act, with a snapshotQuality verdict; call it before acting and after navigation. Interactive elements only, capped on busy screens (filter finds the rest). A trailing " -" marks a non-clickable element. Refs stay stable while the element stays.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "qa_snapshot"
  }
}

Input Schema

Name	Required	Description
`diff`	No	Same screen: only added/removed/changed refs since the previous snapshot; a new screen returns the full list.
`filter`	No	Substring match on text/label/id/role (finds capped elements).
`sessionId`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`diff`	No
`screen`	No
`elements`	No
`elementCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses real behavioral traits: interactive elements only, results are capped on busy screens, filter recovers capped elements, a trailing " -" flags non-clickable elements, and refs remain stable while the element persists. That is exactly the operational nuance an agent needs to interpret refs correctly.

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?

Four tight sentences, front-loaded with the core read semantics and followed by the constraints. Telegraphic phrasing ("Refs stay stable while the element stays") is dense but earns its place; no filler.

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?

An output schema exists, so return values need not be described. The description covers the remaining gaps an agent must know: element addressing form, capping and its workaround, non-clickable marking, and ref lifetime.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the 67%-covered schema for filter: it is the recovery path for elements dropped by capping, not just a substring search. diff and sessionId semantics are left to the schema, which is acceptable given the diff property is already documented there.

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?

Specific verb and resource: "Read the current screen as addressable elements (@e1, @e2...)", plus the return artifact (snapshotQuality verdict) and the consumer (qa_act). It is clearly distinguishable from qa_act, which performs actions rather than reads state.

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?

Explicit timing guidance: "call it before acting and after navigation", and it points to the filter mechanism when capping hides elements. It does not spell out exclusions (e.g., non-interactive content is not returned), but the when-to-call condition is unambiguous.

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