Skip to main content
Glama
vision-gesture-control

vision-gesture-control

by 1nc0gn30

vision_classify_face

Classifies facial landmarks to detect mouth opening, smiles, eye blinks, and eye aspect ratios for touchless gesture control and facial telemetry.

Instructions

Evaluates facial landmarks or features for mouth opening, smile expression, eye blinks, and eye aspect ratios (EAR).

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_classify_face"
  }
}

Input Schema

NameRequiredDescriptionDefault
face_landmarksNoFacial landmark points array (MediaPipe Face Mesh 468 points or key points dict).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden alone. It does disclose the computed features, but not the return shape (booleans vs. numeric EAR values), threshold defaults, or whether the computation is purely local/stateless.

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?

A single front-loaded sentence with no filler; the computed signals are listed compactly. There is no structural padding, though it could fold in one clause about expected input origin.

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 one-parameter compute tool with no output schema, the description should at least characterize what is returned, since nothing else in the structured data does. The listed features partially compensate but leave the response format ambiguous.

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?

With a single parameter at 100% schema description coverage, the schema already explains the MediaPipe 468-point landmark array. The description's phrase 'landmarks or features' hints at an alternative input form but does not clarify how feature dicts should be structured.

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 ('Evaluates') and resource (facial landmarks/features) and enumerates the exact signals computed: mouth opening, smile, eye blinks, EAR. That distinguishes it from sibling classifiers like vision_classify_gesture or vision_analyze_dual_hands, though it does not explicitly name those alternatives.

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 gives no when-to-use guidance, no prerequisites (e.g., landmarks must come from MediaPipe Face Mesh or equivalent), and no indication of when to prefer a sibling tool. The agent must infer the calling context entirely.

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