Skip to main content
Glama

Outil.io

Track video subject

track_video_subject
Read-only

Suivre une zone détaillée d’un rush sur 30 secondes maximum. Retourne les centres normalisés horodatés source, confidence et lostAt ; n’altère pas le montage. Vérifier les points avant de créer des keyframes.

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>",
      "start": "<start>",
      "end": "<end>",
      "region": "<region>"
    },
    "name": "track_video_subject"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
regionYes
assetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, and the description usefully reinforces this ('n'altère pas le montage') while adding the 30-second cap and the return payload (normalized centers with source timestamps, confidence, lostAt) — valuable because no output schema exists. What it omits is failure behavior: what happens when the requested span exceeds 30 seconds, or how lostAt should be interpreted.

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?

Three short, front-loaded sentences with no filler: scope and duration first, return shape second, workflow caution last. Dense and efficiently ordered, though the final caution sentence could be tied more explicitly to a tool.

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

Completeness4/5

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

For a compute-style tool with no output schema and a nested parameter object, the description covers the essential angles: duration limit, return contents, and non-mutating behavior. The remaining gap is parameter-level detail, which the schema does not supply either.

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 0% for 4 required parameters, including a nested region object with non-obvious 0.06–0.7 width/height bounds. The description only partially compensates: 'zone détaillée' hints at region, 'sur 30 secondes maximum' constrains end relative to start, and 'centres normalisés' hints at the normalized coordinate domain — but assetId, the start/end semantics, and the region size limits are all left undocumented.

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 ('Suivre' / track) and resource ('une zone détaillée d'un rush'), plus a hard scope bound of 30 seconds, which separates it from general asset-inspection or keyframe-editing siblings. It doesn't name a sibling tool directly, but the reference to keyframes situates it in the workflow.

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

Usage Guidelines4/5

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

Gives clear usage context: track a detailed region for at most 30 seconds and verify the returned points before creating keyframes, which implies this is an upstream, exploratory step. It stops short of naming a specific alternative or an explicit when-not-to-use case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.