CineFlow Studio

cineflow_nodes_catalog

Lists verified ComfyUI custom nodes needed for video, turnaround, and speech generation, including git clone URLs, so you can install the required dependencies correctly.

Instructions

List all verified ComfyUI custom nodes required for video, turnaround, and speech generation with git clone URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cineflow_nodes_catalog"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "List" implies a non-mutating read, and "verified" plus "with git clone URLs" discloses something about the curation and payload, but it never states whether results are static or fetched live, whether installation state is included, or how the list is ordered or sized.

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?

A single front-loaded sentence with the scope and the key return detail in the first line. No filler, no restating of the tool name as a separate clause.

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 zero-parameter listing tool with no output schema, the description covers what is listed, the category scope, and one concrete field (git clone URLs). It stops short of saying whether the catalog is exhaustive or filtered and what an agent should do with the result next, which matters given install_node sits alongside it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no fabricated parameter guidance.

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 and resource: "List all verified ComfyUI custom nodes," and narrows scope to nodes "required for video, turnaround, and speech generation" plus the payload detail "with git clone URLs." The word "nodes" distinguishes it from the sibling catalogs cineflow_models_catalog and cineflow_workflows_catalog, though the description does not explicitly say so.

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

Usage Guidelines2/5

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

No when-to-use statement, no prerequisites, and no routing to the obvious next step such as cineflow_install_node, cineflow_check_updates, or cineflow_generate_dependency_script. The agent must infer that this is a pre-install discovery step from the word "required" alone.

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

Deploy Server