Skip to main content
Glama

Create motion reactive

create_motion_reactive

Analyze video from camera, file, or synthetic source to produce motion and brightness channels, enabling parameter binding for interactive reactivity.

Instructions

Build a video-analysis chain that exposes ready-to-bind reactive channels — overall brightness plus frame-to-frame motion energy — on a Null CHOP. The camera counterpart to extract_audio_features: bind any parameter to op('…/motion_reactive/features')['motion'] and it responds to movement in front of the camera, or ['brightness'] to ambient light. A Sensitivity knob scales both. Source can be the live camera (may prompt for macOS permission), a movie file, an animated synthetic pattern (for testing without a camera), or an existing TOP. Optical flow is unavailable on macOS, so direction isn't exposed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoVideo source. 'camera' = live webcam/capture device (the real-world default; creating it may pop a one-time macOS camera-permission dialog — click Allow). 'file' = a movie file. 'synthetic' = an animated noise pattern, handy for testing without any device permission. 'existing_top' = analyze a TOP you already have.camera
movie_file_pathNoMovie file path (source='file').
existing_top_pathNoPath of an existing TOP to analyze (source='existing_top').
analysis_resolutionNoThe video is downsized to this square resolution before analysis — small keeps it cheap (the reactive values barely change with size).
expose_controlsNoExpose a live 'Sensitivity' knob (a gain over every feature channel).
parent_pathNo/project1
Behavior4/5

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

Annotations are sparse (readOnlyHint=false, destructiveHint=false, openWorldHint=true). Description adds behavioral details: macOS permission prompt, optical flow unavailability on macOS, downsizing to analysis_resolution, and exposure of Sensitivity knob. No contradiction.

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?

Two sentences, front-loaded with main purpose, followed by details. Efficient but could be slightly more concise without losing information.

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?

Describes source options, macOS caveat, and output channels, but does not specify the exact output format or return value of the Null CHOP. Given no output schema, this is a minor gap.

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 has 83% description coverage (5 of 6 params have descriptions). Description adds integration context but does not significantly enhance individual parameter understanding beyond schema.

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

Purpose5/5

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

The description clearly states the tool builds a video-analysis chain with brightness and motion energy channels on a Null CHOP. It distinguishes from sibling extract_audio_features by calling it the 'camera counterpart.'

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

Usage Guidelines4/5

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

Provides clear context for binding parameters and mentions Sensitivity knob and source options with macOS permission caveat. Does not explicitly state when not to use or list alternatives beyond the one sibling reference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server