vision-gesture-control
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vision_analyze_dual_handsC | Analyzes dual-hand spatial geometry, wrist-to-wrist span, index span, dual pinch state, and dynamic ROI filter lens bounding box coordinates. |
| vision_get_shader_filtersA | Returns all available real-time optical shader filters (Matrix Rain, Thermal IR, Sobel Neon, Cyber VHS, Hologram, Solar Amber) and their hand gesture triggers. |
| vision_get_solfeggio_frequenciesB | Returns the 9 sacred Solfeggio acoustic frequencies (174Hz to 963Hz) and spatial audio Theremin mapping equations. |
| vision_classify_gestureB | Classifies 21 3D/2D hand landmarks (MediaPipe format) into gesture types (e.g. open_palm, fist, pointing_up, peace_sign, pinch, thumbs_up, rock_on, ok_sign) with confidence score, pinch metrics, and individual finger extension states. |
| vision_calculate_dwellB | 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. |
| vision_classify_faceB | Evaluates facial landmarks or features for mouth opening, smile expression, eye blinks, and eye aspect ratios (EAR). |
| vision_generate_action_mapB | Generates complete gesture-to-action key bindings for presentations, media players, drawing studios, air gaming, or accessibility navigation. |
| vision_get_diagnosticsC | Returns system, camera, display server, and compute telemetry diagnostics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes defined by verb+resource (classify vs calculate vs generate). The only plausible confusion is between vision_analyze_dual_hands and vision_classify_gesture, since both consume hand landmarks, though one is dual-hand spatial geometry and the other is single-hand gesture typing. The two static config getters (shader filters, solfeggio frequencies) are distinct but feel like a different category of tool.
All eight tools use the same vision_ prefix plus a snake_case verb_noun pattern (analyze_, get_, classify_, calculate_, generate_). Verbs are chosen meaningfully (get for static data, classify for inference, calculate for computation), with no mixed conventions.
Eight tools is a well-scoped size for a gesture-control server, covering perception, classification, interaction, and diagnostics. A couple of the static-data getters (shader filters, solfeggio frequencies) are tangential flavor rather than core capability, slightly diluting focus.
Core pipeline is covered: hand/face analysis, gesture classification, dwell triggering, action-map generation, and diagnostics. However, there is no temporal/sequence tracking (gestures over time), no pointer/smoothing or coordinate-mapping tool despite dwell-by-position interaction, and no calibration step, leaving gaps for continuous control workflows.