Skip to main content
Glama
Sign In
agent-video-engine

agent-video-engine

by ferdy252
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

revision_compare

Read-only

Compare two saved video revisions to see changes in cuts, graphics, captions, settings, and output duration; render either revision for review.

Instructions

Compare two saved revisions, including changes to cuts, graphics, captions, settings and output duration. preview_render can render either revision.

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": {
      "projectDir": "<projectDir>",
      "fromRevision": "<fromRevision>",
      "toRevision": "<toRevision>"
    },
    "name": "revision_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path of the local video project directory
toRevisionYes
fromRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive operation. The description adds useful behavioral context by specifying what kinds of changes are compared and by clarifying the relationship to preview_render, though it does not describe the comparison result format or whether the comparison is textual versus visual.

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 two efficient sentences with the core comparison purpose front-loaded. Every clause adds relevant information: the compared aspects and the alternative preview_render path.

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 a simple read-only comparison tool, the description covers purpose, comparison scope, and one related alternative. However, with no output schema, it does not explain the shape of the comparison result, and the revision identifier semantics remain under-specified.

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 33%, with projectDir documented but fromRevision and toRevision left without schema descriptions. The description says two revisions are compared, but it does not explain parameter ordering, whether fromRevision is the baseline, or how revision identifiers are obtained, so it does not compensate for the coverage gap.

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: compare two saved revisions. It also enumerates the compared aspects (cuts, graphics, captions, settings, output duration) and distinguishes the tool from preview_render, which handles rendering rather than comparison.

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?

The description implies the tool should be used for comparing revisions and points to preview_render for rendering either revision. However, it gives no explicit when-to-use guidance against revision_list, revision_restore, or project_inspect, and no prerequisites or exclusions are stated.

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

Deploy Server

Other Tools