Skip to main content
Glama

Create pointer reactive

create_pointer_reactive

Turn mouse pointer position and click into normalized u/v, velocity, and button channels exposed on a Null CHOP, ready to bind. Optionally includes a visible feedback trail.

Instructions

Turn mouse/pointer position and click into a first-class creative seed. Builds a Mouse In CHOP → normalized u/v (0..1) + velocity (vu/vv) + button, exposed on a 'pointer' Null CHOP ready for binding: op('…/pointer_reactive/pointer')['u'] / ['v'] / ['button'] / ['vu'] / ['vv']. A Sensitivity knob gains every channel. By default also builds a small visible demo — a bright dot that follows the pointer and leaves a decaying trail over a feedback field — so you immediately see it working; set demo=false to build only the CHOP chain (no image, no preview). multitouch is reserved for a future Panel-COMP touch source; this build always uses Mouse In and reports the limitation as a warning when requested. Creates a new baseCOMP under parent_path. Returns a summary plus a JSON block with the container path, created node paths, the pointer Null path, channel names, exposed controls, any node errors, and warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
demoNoAlso build a visible feedback-field demo the pointer pushes, so you see it working immediately (a bright dot that trails behind the mouse over a decaying feedback field).
multitouchNoWhen true, note that true multitouch needs a Panel COMP touch source; this build always uses Mouse In (single pointer) and reports the limitation as a warning. Kept for forward-compat — it does not change what gets built.
resolutionNoOutput resolution [width, height] in pixels for the demo feedback field.
parent_pathNoParent network where the pointer-reactive container is created (default '/project1')./project1
sensitivityNoGain applied to every pointer channel (u, v, velocity, button) before the output.
Behavior4/5

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

Annotations indicate readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds context about creating a baseCOMP, exposing a Null CHOP, and returning a summary/warnings. It does not contradict annotations and explains the non-destructive nature of the build.

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 detailed but efficient, front-loading the main purpose and then specifying the demo and node details. Each sentence adds value, though it could be slightly trimmed without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters, no output schema, and is a creation tool, the description thoroughly explains what is built (CHOP chain, Null, demo), how to control it (parameters), and what is returned (path, warnings). It leaves no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes beyond schema by explaining how parameters like 'demo' affect the visible output, 'sensitivity' gains all channels, and 'multitouch' is reserved for future. This adds meaningful usage context.

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 'turns mouse/pointer position and click into a first-class creative seed' and details the CHOP and Null outputs. It distinguishes itself from siblings by focusing on pointer-reactive functionality, not just a generic creation tool.

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?

The description explains when to use demo=false (to build only the CHOP chain) and mentions the multitouch limitation. However, it does not explicitly compare against other creation tools or provide exclusion criteria, leaving some ambiguity about when this tool is preferred.

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