Skip to main content
Glama
IlyasKhallouki

hypruse

by IlyasKhallouki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

zoom

Read-only

Capture a native-resolution screen area around a point on a Hyprland desktop, then refine target coordinates on the image so an agent can click accurately.

Instructions

Native-resolution re-capture around a point: the precision step of the coarse-to-fine loop. Screenshot first, estimate the target's global x,y, zoom there, re-estimate on the zoomed image (scale ~1.0, so global = geometry[:2] + image_pixel), then click. size "WxH" in logical pixels (default 480x360) is clamped to the screen; window (an address from desktop, on screen) clamps to that window instead. The metadata echoes the requested point back as point; stable=true waits for the frame to settle first; lossless=true returns PNG.

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
sizeNo
stableNo
windowNo
losslessNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.4
  2. Removedv0.6.0
  3. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / lossless
      Added value: +{
+  "default": false,
+  "title": "Lossless",
+  "type": "boolean"
+}
  4. Addedv0.4.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond them: size defaults to 480x360 and is clamped to the screen (or to `window`), metadata echoes the requested point back as `point`, stable=true waits for the frame to settle, and lossless=true returns PNG. These are exactly the traits an agent needs to predict output and side effects.

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?

Purpose is front-loaded and every sentence carries information about a parameter or behavior. It is dense and slightly run-on, with workflow instructions for the agent folded into the tool description, but there is little genuine waste.

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

Completeness5/5

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

An output schema exists, so return values need not be enumerated, yet the description still notes that metadata echoes the point back as `point`. Combined with clamping rules, defaults, and the settle/PNG flags, an agent has everything needed to invoke it correctly in the coarse-to-fine loop.

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 description coverage is 0%, so the description must carry the burden, and it does: size is described as 'WxH' in logical pixels with a default and clamping rule, window is defined as an address from desktop that changes the clamp target, and stable/lossless are both explained with their effects. Only x/y are left implicit, but the workflow sentence pins them as global 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?

States a specific verb+resource: 'Native-resolution re-capture around a point'. It also positions the tool in a workflow as 'the precision step of the coarse-to-fine loop', which implicitly distinguishes it from the coarse sibling (screenshot). An agent can tell what this does without opening the schema.

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

Usage Guidelines4/5

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

The embedded sequence ('Screenshot first, estimate the target's global x,y, zoom there, re-estimate..., then click') gives clear context for when this tool is used in the loop. It does not name alternatives or exclusions explicitly, so it stops short of a 5 despite being highly actionable.

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

Deploy Server

Other Tools