Skip to main content
Glama
vision-gesture-control

vision-gesture-control

by 1nc0gn30

vision_analyze_dual_hands

Analyzes dual-hand spatial geometry, wrist-to-wrist and index spans, dual pinch state, and dynamic ROI filter lens bounding box coordinates for touchless gesture control.

Instructions

Analyzes dual-hand spatial geometry, wrist-to-wrist span, index span, dual pinch state, and dynamic ROI filter lens bounding box coordinates.

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": {
      "hand0_landmarks": "<hand0_landmarks>",
      "hand1_landmarks": "<hand1_landmarks>"
    },
    "name": "vision_analyze_dual_hands"
  }
}

Input Schema

NameRequiredDescriptionDefault
hand0_landmarksYesArray of 21 3D landmarks for primary hand (Left).
hand1_landmarksYesArray of 21 3D landmarks for secondary hand (Right).
confidence_thresholdNoConfidence threshold (default: 0.5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It lists analysis dimensions but does not state whether the tool is read-only, what it returns, how confidence_threshold affects results, or any side effects or error behavior.

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?

The description is a single front-loaded sentence with no filler. It is dense but appropriately sized for the tool.

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?

For a 3-parameter analysis tool with no output schema and no annotations, the description identifies the analyzed quantities but omits return-value structure and broader behavioral context. It is minimally adequate but leaves meaningful gaps.

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%, and the schema documents all three parameters including the landmark arrays and confidence threshold. The description adds no parameter-level meaning beyond what the schema already provides.

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 ('Analyzes') and enumerates the dual-hand geometry, wrist-to-wrist span, index span, pinch state, and ROI bounding box it operates on, making the resource clear. It does not explicitly differentiate from sibling vision tools such as vision_classify_gesture, so it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no named alternatives. The only implied usage is that it applies to dual-hand landmark inputs.

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