Skip to main content
Glama
vision-gesture-control

vision-gesture-control

by 1nc0gn30

vision_calculate_dwell

Calculates dwell progress for a pointer inside a target zone, returning normalized progress, trigger state, remaining time, and dwell status for gesture-controlled selection.

Instructions

Evaluates dwell progress for a pointer inside a target interactive bounding box zone. Returns normalized progress (0.0 to 1.0), trigger state, remaining time, and dwell status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "x": "<x>",
      "y": "<y>",
      "zone": "<zone>"
    },
    "name": "vision_calculate_dwell"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesPointer X coordinate (normalized 0.0 - 1.0 or pixel space).
yYesPointer Y coordinate (normalized 0.0 - 1.0 or pixel space).
zoneYesTarget zone bounding box as {'x', 'y', 'width', 'height'} or [x, y, w, h].
elapsed_msNoElapsed dwell time inside zone in milliseconds (default: 0.0).
duration_msNoTarget dwell trigger duration in milliseconds (default: 1000.0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully names the return fields (normalized progress, trigger state, remaining time, dwell status), but does not disclose side effects, idempotency, or how trigger state and dwell status are determined.

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 two sentences with zero waste. The purpose is front-loaded and the return values are listed efficiently, with no unnecessary wording.

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

Completeness3/5

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

The tool has five parameters including a nested object, no annotations, and no output schema. The description lists return values and states the core purpose, which is enough to call the tool, but it omits usage context and behavioral details that would help an agent know when and how safely to invoke it.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all five parameters including the nested zone object. The description adds no additional parameter semantics beyond what the schema provides, making the baseline score of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Evaluates dwell progress for a pointer inside a target interactive bounding box zone.' This clearly distinguishes it as a dwell-time calculation tool rather than a classifier or diagnostics tool. However, it does not explicitly contrast itself with any sibling tool.

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

Usage Guidelines2/5

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

The description implies usage by stating what the tool evaluates, but gives no explicit when-to-use guidance, prerequisites, or alternatives. Nothing tells the agent when to call this versus other vision tools or what conditions make the calculation valid.

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