Skip to main content
Glama
vision-gesture-control

vision-gesture-control

by 1nc0gn30

vision_generate_action_map

Generates complete gesture-to-action key bindings for presets such as presentations, media players, drawing, gaming, and accessibility navigation, with optional custom overrides.

Instructions

Generates complete gesture-to-action key bindings for presentations, media players, drawing studios, air gaming, or accessibility navigation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vision_generate_action_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNoPreset action map category.presentation
overridesNoOptional custom key/action overrides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says what is generated but omits whether the operation is pure/safe, what permissions are needed, how overrides are merged or validated, and what the response contains. The domain list alone is insufficient for a tool with no annotations.

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?

A single front-loaded sentence that states the action and lists examples without filler. Every phrase contributes to identifying the tool's intended domains.

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 only two optional parameters and a well-described schema, and the description makes the core generation purpose clear. But with no annotations and no output schema, it should say more about the returned mapping and override behavior to fully support correct invocation.

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 preset enum and overrides object are already documented in the schema. The description echoes the preset categories but adds no detail about override merge/replace behavior or accepted key syntax, so it meets only the baseline expectation.

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?

States a specific verb and resource: generates gesture-to-action key bindings. The enumerated domains (presentations, media players, drawing, gaming, accessibility) make the purpose concrete. It does not explicitly differentiate from siblings, but the function is clearly distinct.

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?

Lists relevant use contexts such as presentations, media players, drawing studios, air gaming, and accessibility navigation, which implies when the tool is useful. However, it does not compare against alternatives, state prerequisites, or say when not to use it.

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