Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_install_node

Clones or updates a ComfyUI custom node into custom_nodes and installs its requirements.txt dependencies, enabling CineFlow Studio workflows to add needed node extensions.

Instructions

Clone or update a ComfyUI custom node into custom_nodes/ and install its requirements.txt dependencies.

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": {
      "node_name": "<node_name>"
    },
    "name": "cineflow_install_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
git_urlNoOptional custom git repository URL.
comfy_dirNoTarget ComfyUI directory (default: 'ComfyUI').
node_nameYesName of custom node (e.g. 'ComfyUI-LTXVideo').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden and does disclose the two main side effects: writing into custom_nodes/ and running requirements.txt installation. It does not say whether an existing node is overwritten or fails, whether it needs network/git access, whether the install is idempotent, or what happens if pip resolution fails.

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?

A single front-loaded sentence with the action, destination, and side effect stated compactly with no filler. It is arguably too terse for a mutating installer, but structurally it wastes nothing.

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 3-parameter, no-annotation, no-output-schema mutation tool, the description covers what it does but not idempotency, failure modes, or permissions. It is minimally adequate rather than complete.

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 all three parameters are already documented in the schema, establishing a baseline of 3. The description mentions the target directory and requirements install but adds no per-parameter meaning (e.g. default node_name behavior or comfy_dir implications) beyond the schema.

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 uses specific verbs ('Clone or update') with a concrete resource (a ComfyUI custom node) and states the destination ('custom_nodes/') plus the dependency-install side effect. It is clearly distinguishable from catalog/inspection siblings, though it never names an alternative.

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?

There is no explicit guidance on when to call this versus siblings such as cineflow_nodes_catalog, cineflow_check_updates, or cineflow_apply_update. The use case is only implied by the 'install/update a node' phrasing; no prerequisites, no exclusions, no 'use X instead' routing.

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