Dittu

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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations exist; description explains return format, normalized points, perspective warp, and warns about quadrilateral nature and asymmetric adjustments.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Clear and front-loaded with purpose. Two paragraphs; slightly verbose but all sentences add value.

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?

No output schema; description sufficiently explains return format and semantics for a parameterless 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?

No parameters; baseline 4. Description adds meaning about return structure and coordinates.

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?

Clearly states verb 'Get' and resource 'phone's current screen-corner calibration'. Distinguishes from sibling 'set_corners' by being the read counterpart.

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?

Implied usage for reading calibration, but no explicit when-to-use, prerequisites, or comparison with alternatives like 'set_corners'.

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

All Dittu tools Inspect

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.6/5.0

Disambiguation5/5

Each tool targets a distinct action: clicks, screenshots (raw, corrected, calibration aids), keyboard input, mouse movement, scrolling, and corner calibration. There is no ambiguity between tools.

Naming Consistency3/5

Tool names mix conventions: some are single verbs (click, scroll, key), some are verb_noun (move_mouse, set_corners, type_text), and some are longer phrases (take_screenshot_with_crosshair). Although readable, the inconsistency is notable.

Tool Count5/5

With 12 tools, the server covers all essential interactions for camera-based screen control without being bloated or sparse. Each tool has a clear role.

Completeness4/5

The tool set covers clicking, typing, key combinations, mouse movement, scrolling, and multiple screenshot modes including calibration aids. Missing drag/swipe functionality is a minor gap.

Resources

Need Help?