Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_vision_inspect

Evaluate keyframes with Qwen Vision inside ComfyUI: score quality, detect defects, verify closed-mouth lip-sync, check continuity, and auto-caption references without VRAM conflicts.

Instructions

Inspect and evaluate keyframes/takes via Qwen 3.8 Vision co-located inside ComfyUI: aesthetic quality, artifact/defect detection, lip-sync closed-mouth guard (Issue #600), and English reference auto-captioning without VRAM conflicts.

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": {
      "image_path": "<image_path>"
    },
    "name": "cineflow_vision_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoVisual CV task to perform.
comfy_urlNoOptional ComfyUI base URL (default: http://127.0.0.1:8188).
image_pathYesPath to input frame or reference photo.
check_closed_mouthNoWhether to verify lips are closed for silent or voiceover shots (Rule D).
previous_frame_pathNoOptional path to preceding shot's frame for continuity scoring.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It adds useful context about running via Qwen Vision co-located inside ComfyUI, avoiding VRAM conflicts, and supporting a closed-mouth guard, but it does not state whether the operation is read-only, what permissions or preconditions apply, or what happens on failure.

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?

The description is a single dense sentence that front-loads the core purpose and then lists capabilities. Most clauses earn their place, though the parenthetical issue reference is slightly less useful than the rest.

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 five-parameter inspection tool with full schema coverage but no output schema, the description explains capabilities but not the shape of the returned result. It leaves gaps around what an inspection produces, such as scores, detected defects, captions, or recommendations, and does not clarify usage relative to alternatives.

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 description coverage is 100%, so the input schema already documents all five parameters and the task enum. The description does not add syntax, default behavior, or constraints beyond what the schema provides, making the baseline score of 3 appropriate.

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?

The description states a specific verb ('Inspect and evaluate') and resource ('keyframes/takes') and enumerates concrete capabilities including quality assessment, defect detection, lip-sync guarding, and auto-captioning. It does not explicitly distinguish itself from any sibling tool, which keeps it short of a 5.

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 is used when visual inspection of keyframes or takes is needed, and lists capability areas that map to tasks. However, it gives no explicit when-to-use versus when-not-to-use guidance and does not name any alternative sibling tool.

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