Capture the screen and overlay a coordinate grid.
step: grid spacing (default 0.1, use 0.05 for finer grid on small UI elements).
Returns a JPEG image with grid drawn on top.
| Name | Required | Description | Default |
|---|---|---|---|
| step | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It mentions the output is a JPEG with grid, which is helpful, but it does not disclose whether the operation is read-only or state side effects, leaving gaps in transparency.
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 two sentences, front-loaded with the core purpose, and every sentence adds value. No wasted words.
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?
For a simple tool with one optional parameter and no output schema, the description covers purpose, output format, and parameter usage. It is mostly complete, though it could mention the entire screen capture and coordinate system.
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 adds significant meaning to the 'step' parameter beyond the schema: it explains grid spacing, default value, and suggests 0.05 for finer grids on small UI elements. Since schema coverage is 0%, the description fully compensates.
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 'Capture the screen and overlay a coordinate grid.' It uses specific verbs and resources, and the grid overlay distinguishes it from siblings like 'take_screenshot' and 'take_screenshot_with_crosshair'.
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 implies use for tasks needing a grid overlay, and provides a parameter tip for finer grid on small UI elements. However, it does not explicitly state when not to use it or name alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: click actions, mouse movement, keyboard input, scrolling, screen captures (raw, calibrated, with grid or crosshair), and calibration. No overlap between tools.
All tools use snake_case verb_noun pattern consistently (e.g., get_corners, take_screenshot, set_corners), with longer names following the same convention (e.g., take_screenshot_with_crosshair).
12 tools are well-scoped for remote computer control and calibration, covering essential actions without being excessive or insufficient.
The set covers core operations (click, type, scroll, screenshot, calibration) but lacks a dedicated drag or right-click tool, which agents may need to work around.