Capture the current Android screen to visually verify UI state. Returns an image plus a text summary, and can overlay numbered boxes to map screen elements.
Capture the current screen as an image so you can visually verify state. Returns the image plus a text summary. Combine with_som=true with get_screen_elements to map numbered boxes to element indices.
| Name | Required | Description | Default |
|---|---|---|---|
| max_dim | No | ||
| with_som | No | ||
| save_path | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states that the tool returns an image and a text summary, making the primary output transparent. It does not mention any side effects, but since it is a screenshot operation, it is implicitly non-destructive; no annotations are present to contradict this.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, consisting of three clear sentences without unnecessary fluff. It efficiently conveys the core action, output, and a useful tip in a well-organized manner.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides sufficient context for the tool's purpose and a specific cross-tool usage scenario. However, it omits details about the effects of 'max_dim' and 'save_path', which could be relevant for users to fully understand the tool's capabilities and constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains the purpose of the 'with_som' parameter, but does not describe the other two parameters ('max_dim' and 'save_path'). Since only one of three parameters is clarified, the description only partially adds meaning beyond the schema's basic type and default information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool captures the current screen as an image for visual verification, which is a specific and unambiguous purpose. It also mentions the output includes an image and a text summary, further clarifying the intended use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a concrete usage hint: combining with_som=true with get_screen_elements to map numbered boxes to element indices. This gives practical guidance on how to use the tool effectively, though it does not explicitly contrast it with alternatives or specify when to prefer it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.