agent-video-engine

Overview Schema Source Related Servers Discussions Admin

draft_inspect

Read-only

Inspect proposed draft changes and verify whether the base revision is still current, with an optional compiled timeline showing draft timing and captions.

Instructions

Inspect proposed changes and whether the base revision is still current. Optional compiled timeline includes draft timing and captions.

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>",
      "draftId": "<draftId>"
    },
    "name": "draft_inspect"
  }
}

Input Schema

Name	Required	Description
`draftId`	Yes
`projectDir`	Yes	Absolute path of the local video project directory
`includeTimeline`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Nov 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the staleness-check behavior and explains that timeline compilation is opt-in, but says nothing about whether the call errors or degrades when the base revision is stale, nor what the inspection yields.

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 compact sentences with the core purpose front-loaded and the optional parameter detail trailing. The second sentence is telegraphic ("Optional compiled timeline includes...") and slightly awkward, but nothing is wasted.

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 3-parameter read tool with no output schema, the definition is broadly adequate, but it omits what the inspection actually returns (a diff? a status flag?) and leaves one parameter undocumented. An agent can invoke it, but not confidently interpret or scope the 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 33%, so the description needs to compensate. It partly does by explaining includeTimeline ("compiled timeline includes draft timing and captions"), but draftId is left entirely unexplained in both schema and description, and the cost/side-effect of enabling the timeline compile is not stated.

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?

"Inspect proposed changes and whether the base revision is still current" gives a concrete verb (inspect) plus the two things being checked (draft changes, base-revision staleness). It is clear on its own, but it never distinguishes itself from siblings like draft_list, revision_compare, or draft_apply, which an agent must choose between.

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?

Usage is only implied: mentioning whether the base revision is still current hints at a pre-apply sanity check before draft_apply, but the description never states "call this before applying" or names an alternative. No exclusions or prerequisites are given.

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