Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Track point

track_point

Tracks a specified point through its shot and records a world-track definition. The seed uses program time and normalized picture coordinates.

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": {
      "t": "<t>",
      "x": "<x>",
      "y": "<y>",
      "project_id": "<project_id>"
    },
    "name": "track_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
tYes
xYes
yYes
idNo
endNo
labelNo
startNo
radiusNo
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare a non-readonly, non-idempotent, non-destructive closed-world mutation, so the safety profile is covered. The description adds real value by saying a persistent 'world-track definition' is recorded and that the seed is expressed in program time and normalized picture coordinates. It does not disclose what happens to an existing track on repeat calls (relevant given idempotentHint=false) or whether the track extends beyond the shot.

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 action front-loaded and the seed-coordinate convention second; no filler or duplication. The second sentence is dense jargon ('world-track definition', 'program time') but each clause carries information, so nothing is wasted.

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 9-parameter mutation with 11% schema coverage and no output schema, the description is thin: it says nothing about what is returned, how start/end/radius define the track's extent, or what a label or id does. The agent can form the seed point but not a complete correct invocation.

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 description coverage is 11% — only project_id is documented — so the description must carry weight, and it does explain that t/x/y are the seed in program time and normalized picture coordinates. However, five parameters (id, start, end, radius, label) receive no semantic explanation anywhere, and 'program time' units and the normalized coordinate origin are still ambiguous.

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 resource: 'Tracks a specified point through its shot and records a world-track definition.' That distinguishes it as a tracking/world-definition writer rather than a pure lookup. It never names or contrasts with related siblings such as place_in_world, pin_to_plane, or remove_world, so the agent must infer the boundary from the name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance, no prerequisite about the point needing to lie within a shot, and no mention of alternatives. The phrase 'through its shot' implies the tool operates on footage in the current project, but the agent gets no routing signal versus the many add_/set_/place_ siblings.

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 toolsInspect
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.

Resources