Skip to main content
Glama

ios_screenshot

Capture a PNG screenshot from an unjailbroken iOS or iPadOS device, using WebDriverAgent when available or falling back to DVT screenshot capture.

Instructions

Capture screen PNG (via WDA if running, else DVT Screenshot).

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

Input Schema

NameRequiredDescriptionDefault
filenameNogrogu_latest.png

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavioral burden. It usefully discloses the fallback mechanism (WDA if running, otherwise DVT Screenshot), which tells the agent behavior depends on runtime environment. However, it omits key traits: that invoking it writes a file to disk (a side effect), where that file lands, and what happens if neither backend is available.

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?

A single compact sentence with the action front-loaded and no filler. Every clause earns its place, including the backend fallback note.

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

Completeness2/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 needn't be explained, but the description still leaves out essentials for a file-writing tool: required device/session state, output location, and any meaning for the filename parameter. For a screenshot tool with a side effect, this is thin.

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

Parameters2/5

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

Schema description coverage is 0% and there is one parameter, so the description must compensate. It says nothing about "filename" — not where the file is written, whether a path is accepted, or that a default name (grogu_latest.png) is used — leaving the agent to infer semantics from the schema alone.

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?

States a concrete verb and resource ("Capture screen PNG") that unambiguously distinguishes it from sibling action tools like ios_tap, ios_swipe, and ios_ui_dump. It does not explicitly name or contrast a sibling, but the purpose is specific enough to select correctly.

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

Usage Guidelines3/5

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

Usage is only implied by the name and purpose — an agent can infer it's for grabbing a screenshot of the device. There is no explicit when-to-use guidance, no statement of prerequisites (e.g., a booted simulator/device or an active session), and no mention of alternatives such as ios_ui_dump for inspecting the element tree.

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