Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_workflow_get

Retrieves the exact ComfyUI JSON node graph blueprint for a specified workflow template, so you can inspect or reuse its structure.

Instructions

Retrieve the exact ComfyUI JSON node graph blueprint for a specific workflow template.

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": {
      "workflow_id": "<workflow_id>"
    },
    "name": "cineflow_workflow_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflow_idYesWorkflow identifier (e.g. 'ltx_video_img2vid', 'flux_character_turnaround').

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 supplied, so the description carries the full disclosure burden. 'Retrieve the exact ... blueprint' implies a deterministic read of a canonical template, but the description says nothing about error behavior for unknown workflow IDs, authentication needs, payload size, or whether templates are versioned.

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 no filler or redundancy. It is efficient, though its brevity means several useful facts are absent rather than trimmed.

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 one-parameter read tool with no output schema, the description should at least sketch what the returned blueprint looks like or how it feeds execution. It names the return artifact ('ComfyUI JSON node graph') but stops short of describing its structure or intended downstream use.

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% and the workflow_id property already documents itself with two concrete example values. The description adds no further meaning about identifier format or sourcing, so it neither compensates for nor improves on 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 a specific verb ('Retrieve') and a specific resource ('exact ComfyUI JSON node graph blueprint for a specific workflow template'), so an agent knows it fetches a template definition rather than running anything. It does not explicitly name the sibling it differs from (cineflow_comfy_workflow_execute), leaving the execute-vs-fetch distinction to inference from the word 'blueprint'.

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 statement of when to call this versus cineflow_comfy_workflow_execute or cineflow_comfy_config_get, and no prerequisites such as needing a valid workflow_id from a catalog. The only usage signal is implicit in 'blueprint', which suggests inspection rather than execution.

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