Skip to main content
Glama

Vidova

by ai.vidova
OverviewDiscussionsAdmin

Find what passes in front of a surface

track_occluders

Find what passes in front of a tracked surface, so a picture pinned to it stays behind a person, a hand or a car. It finds what query names on every frame of the track's source range, as segment_subject does, and keeps it where it covers the surface: what the camera sees over the surface is in front of it. It stores the mask on the track, and then keeps those pixels of the footage in front of the pinned picture. The answer gives the mask Asset ID, the times something covers the surface, and the pin to write. When nothing covers the surface, nothing is stored. Run it after track_plane, and again after you split or merge the track. Uses about 57 credits a minute of the track's range, billed by the second, as segment_subject. Read builtin-object-tracking first.

Input Schema

NameRequiredDescriptionDefault
atYesA source second where it is in front of the surface and all of it shows, which you checked with preview_frame. null picks one itself.
queryYesWhat passes in front of the surface, in a few words: "person", "hand", "the red car". null is a person.
trackIdYesThe surface's object track, as track_plane answered it (track_...).
projectIdYesThe project this call runs on without changing the open project. null (or leaving it out) uses the open project. wait_for_jobs takes the projectId of the calls that started the jobs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, the description discloses storage behavior, the no-occluder no-store case, the returned mask Asset ID and covering times, the pin usage, and the credit cost of about 57 credits per minute billed by the second. These are substantial operational details for a non-read-only, non-idempotent 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?

The description is front-loaded with the tool's purpose and then proceeds through mechanism, output, edge case, prerequisites, and cost. Every sentence adds a distinct operational fact, and the length is justified by the tool's multi-step behavior.

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?

With no output schema and limited annotations, the description still covers what the tool returns, what gets stored, when storage is skipped, prerequisites, and cost. An agent has enough information to decide when and how to call it.

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 100%, so the input schema already carries the parameter documentation. The description adds some conceptual meaning for query and trackId, but does not explain the at parameter or add syntax beyond the schema.

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 states a specific verb and resource: finding what passes in front of a tracked surface, and explains the practical effect on a pinned picture. It distinguishes itself from segment_subject by noting that it keeps only the portions covering the surface and stores the resulting mask on the track.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit sequencing: run after track_plane, run again after splitting or merging the track, and read builtin-object-tracking first. It also states that nothing is stored when nothing covers the surface, and explains the segment_subject comparison.

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

All Vidova 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