Skip to main content
Glama

dittu

by io.github.BorisGujvin
OverviewDiscussionsAdmin

take_screenshot_with_crosshair

Capture the screen, crop tightly around (nx, ny), zoom in, and draw a crosshair
at exactly that expected position.

Use this for screen-corner calibration: move_mouse(nx, ny) near a screen edge,
then call this to see whether the actual cursor lines up with the crosshair
(where it SHOULD be if calibration is perfect). If the cursor is offset from the
crosshair, or missing entirely (edge is cropped out of frame), corners need
adjusting — see get_corners/set_corners.

nx, ny: the same coordinates you passed to move_mouse.
zoom: magnification factor for the cropped region (default 4x).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nxYes
nyYes
zoomNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: crops tightly, zooms, draws crosshair at expected position. Also explains consequences if cursor is offset or missing, which is critical for calibration feedback.

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?

Three sentences, each purposeful. No redundancy, front-loaded with action and purpose. Highly efficient.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, behavior, and parameter semantics well. Lacks explicit mention of return value (likely an image), but given no output schema, it's acceptable. Could be slightly more complete on what the tool returns visually.

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

Parameters5/5

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

Schema coverage is 0%, so description carries full burden. It explains nx, ny are the same coordinates passed to move_mouse and zoom is magnification (default 4x). This adds essential meaning beyond the bare schema.

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?

The description clearly states the action: capture screen, crop around (nx, ny), zoom in, draw crosshair at expected position. It distinguishes from siblings like take_screenshot (no crosshair) and take_screenshot_with_grid (different overlay).

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

Usage Guidelines5/5

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

Explicitly states use case: screen-corner calibration after move_mouse near edge. Mentions alternative tools get_corners/set_corners for adjusting, so the agent knows when not to use this tool.

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

All dittu toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources