Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_comfy_config_set

Save ComfyUI directory paths and API URLs for a project to settings/comfyui.json so AI filmmaking workflows can locate models, custom nodes, and the local ComfyUI service.

Instructions

Configure and save ComfyUI directory paths and API URLs for the project (stored in settings/comfyui.json).

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": {
      "project_id": "<project_id>"
    },
    "name": "cineflow_comfy_config_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
comfy_dirNoPath to local ComfyUI directory.
comfy_urlNoComfyUI API endpoint (e.g. 'http://127.0.0.1:8188').
models_dirNoPath to ComfyUI models directory.
project_idYesProject identifier.
active_profileNoVRAM profile (e.g. 'rtx_24gb', 'rtx_16gb').
custom_nodes_dirNoPath to custom nodes directory.

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?

No annotations are provided, so the description carries the full burden. It usefully discloses that values persist to settings/comfyui.json, which tells the agent changes are durable rather than session-only. It omits important behavior: whether unlisted fields are preserved or wiped, whether paths are validated, and whether a restart is required.

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 efficient sentence with the action front-loaded and the persistence detail appended. No wasted phrasing, though it is quite short for a six-parameter mutation tool.

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?

With six parameters, a mutating write, no annotations, and no output schema, the description should say more about overwrite semantics and prerequisites. It covers what the tool does and where data lands, but leaves an agent without enough to call it safely in every case.

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 100%, so all six parameters including examples like the URL format and VRAM profile are documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 (configure and save) and a specific resource (ComfyUI directory paths and API URLs), and the 'set' vs sibling 'cineflow_comfy_config_get' contrast is inferable from the name. It stops short of explicitly differentiating itself from the getter, but the purpose is unambiguous.

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 explicit when-to-use, when-not, or prerequisites. The parenthetical storage location hints at persistence but gives no guidance on when to call this versus reading config or setting up a project first.

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