Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_interactive

Make a layer tappable or draggable so clicks fire triggers and drags can follow the cursor, drive a parameter, or scrub a timeline.

Instructions

Make a layer interactive: tappable (fires click triggers) and/or draggable (fires drag events). Drag can follow the cursor, drive a parameter (setsParameter), or scrub a timeline (scrubsTimeline).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "layerId": "<layerId>"
    },
    "name": "set_interactive"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerIdYesLayer to make interactive
dragAxisNoDrag axis (default both)
tappableNoFire click triggers on tap
dragRangeNoPx distance for progress=1 (default 200)
draggableNoEnable dragging
requestIdNo
sessionIdNo
followCursorNoLayer follows cursor while dragging
setsParameterNoParameter id set with drag progress 0-1
scrubsTimelineNoTimeline id scrubbed by drag progress
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description must carry behavior. It does add real value by disclosing the side effects — taps fire click triggers, drags fire drag events, and drag progress can drive a parameter or scrub a timeline. But it is silent on the mutation envelope: no mention of revision checks (expectedRevision), idempotency (requestId), session scoping (sessionId), or reversibility, which matters for a write tool.

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?

Two sentences, front-loaded with the core action, followed by the mode enumeration. No filler, no restating of the tool name as a title.

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 an 11-parameter mutation tool with no output schema and no undo documentation, the description covers the interaction semantics but leaves the operational contract thin: expected revision conflicts, request deduplication, and what the tool returns (updated revision?) are all unaddressed. It is adequate for the happy path but not complete for careful use.

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 coverage is 73%, so the schema already documents most parameters with defaults. The description restates setsParameter/scrubsTimeline and followCursor without adding format or semantics beyond the schema, and says nothing about dragAxis, dragRange, expectedRevision, requestId, or sessionId. Baseline 3 holds.

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?

States a specific verb and resource — 'Make a layer interactive' — then immediately enumerates the two capability modes (tappable, draggable) and the three drag variants. This is enough for an agent to distinguish it from siblings like add_trigger, add_binding, or update_layer without opening a schema.

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?

Usage is implied rather than stated: the description frames the tool as the way to enable taps and drags, and names the three drag behaviors (followCursor, setsParameter, scrubsTimeline), which helps pick a mode. However, it never says when NOT to use it, nor points to the trigger/binding/parameter tools that a caller might need first (e.g., add_trigger to define the click trigger that this fires).

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

Deploy Server

Other Tools