Valmera — AI Video Editor

Attach

attach

Attaches an existing motion graphic to a measured face, hand, joint, point, object or plane anchor. Configurable pin, following behavior, occlusion and lost-track handling determine placement; clear detaches the graphic.

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": {
      "motion_id": "<motion_id>",
      "project_id": "<project_id>"
    },
    "name": "attach"
  }
}

Input Schema

Name	Required	Description
`to`	No	face, face.<eye_l\|eye_r\|iris_l\|iris_r\|nose\|mouth\|chin\|forehead\|ear_l\|ear_r>, head, hand.<index_tip\|thumb_tip\|palm\|wrist\|pinch\|frame>, pose.<chest\|shoulder_l\|...>, track:<id>, object:<id>, plane:<id>, screen
`pin`	No
`lock`	No
`lost`	No
`clear`	No
`place`	No
`which`	No	any\|left\|right (on screen)\|0..7
`follow`	No
`offset`	No
`shadow`	No
`smooth`	No
`motion_id`	Yes
`occluders`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / project_id / description

Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."

AddedOct 15, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation, and the description adds real behavioral context: placement is governed by pin, follow, occlusion and lost-track handling, and clear detaches. It still omits what happens if the graphic is already attached, whether attaching replaces prior state, and what lost-track defaults to.

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 tight sentences, front-loaded with the action and anchor targets. The second sentence is compressed to the edge of ambiguity ('Configurable pin, following behavior, occlusion and lost-track handling determine placement') but nothing is redundant.

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

Completeness2/5

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

For a 14-parameter mutation with no output schema and thin schema documentation, the description is too sparse. An agent cannot tell what the call returns, how conflicts with an existing attachment resolve, or what most of the optional knobs mean, so it would have to guess on the majority of parameters.

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

Parameters2/5

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

Schema coverage is only 21% across 14 parameters, so the description must carry more weight. It gestures at pin, follow, occluders and lost, but leaves lock (world/screen), shadow, smooth, offset, place and which's numeric form completely unexplained, and gives no value semantics for the ones it does name.

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 concrete verb and resource: attaches an existing motion graphic to a measured anchor, and enumerates anchor families (face, hand, joint, point, object, plane). The word 'existing' implicitly separates it from add_motion_graphic, but no sibling is named explicitly, so differentiation still requires reading the schemas.

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?

No guidance on when to choose attach over add_motion_graphic, set_motion_graphic, bind_motion_motif, pin_to_plane or track_point, all of which live in adjacent territory. The only routing signal is the incidental 'clear detaches the graphic', which describes an in-tool alternative rather than tool selection.

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

All Valmera — AI Video Editor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.