Valmera — AI Video Editor

Pin to plane

pin_to_plane

Places an existing graphic or new text on a tracked plane or an explicitly supplied four-corner surface. Supports occluders, shadow interaction and blending with the surface.

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

Input Schema

Name	Required	Description
`t`	No
`id`	No
`end`	No
`quad`	No
`text`	No
`blend`	No
`place`	No
`plane`	No
`start`	No
`shadow`	No
`surface`	No
`motion_id`	No
`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

B3.1/5.0

Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent, closed-world write, so safety is covered structurally. The description adds real behavioral color — occluders, shadow interaction, blending with the surface — but omits whether the pin is time-bounded on the timeline, what element it creates, and whether it replaces existing pins.

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 with the placement target front-loaded and the capability list second. No filler, though a few more specifics could have been traded for the generic phrase 'supports occluders, shadow interaction and blending.'

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?

A 14-parameter tool with 7% schema coverage and no output schema needs far more than two sentences. An agent cannot infer the timing parameters, how 'id' references an existing graphic versus supplying 'text', or how motion_id interacts with the plane, so the definition is incomplete for correct invocation.

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 description coverage is only 7% (just project_id), so the description carries the burden and only partly meets it. It usefully clarifies that 'plane' means a tracked plane and 'quad' an explicitly supplied four-corner surface, and gestures at occluders, shadow, and blend, but leaves t, start, end, id, place, motion_id, and surface entirely unexplained.

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 and target ('Places an existing graphic or new text on a tracked plane or an explicitly supplied four-corner surface'), which distinguishes it from add_text or add_element at a glance. It never names those siblings explicitly, but the resource and placement mechanism are concrete enough for an agent to recognize the operation.

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 only implied: pinning is for surfaces that are tracked or explicitly defined by four corners. There is no statement of when to prefer this over add_text, add_motion_graphic, place_in_world, or track_point, and no prerequisites or exclusions are given.

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.