Vidova

Find objects

find_objects

Find named objects on a source frame. Returns numbered detections and an image, and a json block with each box in source, film and film_norm. Standard threshold 0.15, maxResults 8. at is a source second, or a film second with atSpace timeline. Read builtin-object-tracking first.

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": {
      "assetId": "<assetId>",
      "queries": "<queries>",
      "at": "<at>",
      "threshold": "<threshold>",
      "maxResults": "<maxResults>",
      "clipId": "<clipId>",
      "atSpace": "<atSpace>",
      "projectId": "<projectId>"
    },
    "name": "find_objects"
  }
}

Input Schema

Name	Required	Description
`at`	Yes
`clipId`	Yes	The film clip that plays this asset, when space or atSpace needs one and several clips play it. null picks the clip that shows the asset at that time.
`assetId`	Yes
`atSpace`	Yes	What this call's times are. null or source: seconds into the asset file. timeline: seconds of the film, read through the clip that plays the asset then (clipId to pick one).
`queries`	Yes
`projectId`	Yes	The 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.
`threshold`	Yes
`maxResults`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

addedInput schema / properties / atSpace

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "source",
+        "timeline"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "What this call's times are. null or source: seconds into the asset file. timeline: seconds of the film, read through the clip that plays the asset then (clipId to pick one)."
+}

addedInput schema / properties / clipId

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The film clip that plays this asset, when space or atSpace needs one and several clips play it. null picks the clip that shows the asset at that time."
+}

changedInput schema / required

Previous value: -[
-  "assetId",
-  "queries",
-  "at",
-  "threshold",
-  "maxResults",
-  "projectId"
-]New value: +[
+  "assetId",
+  "queries",
+  "at",
+  "threshold",
+  "maxResults",
+  "clipId",
+  "atSpace",
+  "projectId"
+]

First observedOct 19, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, which is slightly surprising for a 'find' operation; the description doesn't clarify what side effect or state change makes it non-read-only, nor any job/latency behavior. It does add genuine context on return shape and coordinate spaces, but the annotation safety profile is left unexplained.

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?

Front-loads the core action and return format, then terse parameter notes and the doc prerequisite; no filler. The telegraphic phrasing ('at is a source second') is dense but readable and short for the amount of information conveyed.

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 8-required-parameter tool with no output schema, the description does cover return structure, defaults, coordinate spaces, and points to reference docs. It still omits the semantics of `queries`, what threshold means, and why the operation isn't read-only — gaps an agent would hit before a first successful call.

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 only 38%, so the description must compensate. It does explain `at` (source vs film seconds), `atSpace`, and gives typical values for `threshold` and `maxResults`, but never explains `queries` (name strings?) or `assetId`, leaving two required parameters undocumented in both places.

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+resource: 'Find named objects on a source frame', and adds what it returns (numbered detections, an image, a json block with boxes in source/film/film_norm). It does not explicitly distinguish itself from sibling detection tools such as track_detection, track_faces or track_box, so an agent must infer the boundary.

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?

Gives a prerequisite ('Read builtin-object-tracking first') and states standard values (threshold 0.15, maxResults 8), which is useful context for calling it. However, it gives no when-to-use/when-not guidance against the many sibling tracking tools, leaving selection to inference.

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

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