Skip to main content
Glama

dittu

by io.github.BorisGujvin

get_corners

Get the phone's current screen-corner calibration.
Returns {"tl": [nx,ny], "tr": [nx,ny], "br": [nx,ny], "bl": [nx,ny]} — each corner
is a normalized point (0.0–1.0) in the RAW camera frame, defining the perspective
warp that maps the camera view onto a flat rectangle representing the monitor.
These four points are an arbitrary quadrilateral (trapezoid), not a bounding box —
adjust one corner at a time without assuming the others move symmetrically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains the return format, semantics of the corner points (normalized, define perspective warp), and warns that it's an arbitrary quadrilateral not a bounding box—adding valuable behavioral context beyond the schema.

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?

The description is a single paragraph with three sentences. It front-loads the purpose, then gives the return format and a key behavioral caveat. 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.

Completeness4/5

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

Given no parameters and no output schema, the description adequately explains what the tool returns and how to interpret the data. It could mention typical usage context (e.g., for calibration before screen actions), but overall it is complete for a simple read tool.

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

Parameters4/5

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

There are zero parameters, and schema coverage is 100%. The description adds no parameter info because none exist, but it explains the tool's output meaning. With 0 parameters, a baseline of 4 is appropriate, and the description provides full context for the return value.

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 tool's action: 'Get the phone's current screen-corner calibration.' It uses a specific verb and resource, and distinguishes itself from sibling tools like set_corners (write) and screenshot tools (different purpose).

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?

No explicit when-to-use or when-not-to-use guidance is given. The description implies usage for reading calibration data before perspective-dependent operations, but does not state alternatives or exclusions.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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).

Tool Count5/5

12 tools are well-scoped for remote computer control and calibration, covering essential actions without being excessive or insufficient.

Completeness4/5

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.

Resources