Capture the RAW camera frame — no perspective warp, no crop to the calibrated
screen quad. Use this to see exactly what the camera sees before any correction,
e.g. when troubleshooting why take_screenshot looks wrong, or before adjusting
corners with get_corners/set_corners.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that no perspective warp or crop is applied, which is the key behavioral trait. Does not mention return format or failure modes, but adequate for a simple read-only tool.
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?
Two sentences, front-loaded action then usage context. Every word earns its place. No redundancy.
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?
Given no params, no output schema, and no annotations, the description is fairly complete: purpose, usage context, behavioral traits. Could mention output is an image, but implied.
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?
No parameters. Schema coverage is 100%. Description adds value by explaining what the tool does with zero config, though it doesn't need to add per-param info. Baseline 4 for no parameters.
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?
Description clearly states it captures the raw camera frame without warp or crop, distinguishing it from take_screenshot. Verb 'capture' and resource 'raw camera frame' are specific and unambiguous.
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?
Explicitly says when to use troubleshooting take_screenshot issues, before adjusting corners. Implicitly not for normal screenshots. Slightly lacking explicit 'when not to use' but clear enough.
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.