Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_comfy_config_get

Retrieve ComfyUI environment paths and the active API URL for a project to configure model, custom node, and output directories correctly.

Instructions

Get ComfyUI environment paths (comfy_dir, models_dir, custom_nodes_dir) and active API URL for the project.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It implies a read-only lookup but never says whether the paths reflect a saved configuration or live filesystem state, what happens for an unconfigured project, or whether the API URL is validated. It does at least list the returned fields, which is useful without an output schema.

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?

One front-loaded sentence that names the fields returned, with no filler. It could be tightened slightly, but nothing in it is wasted.

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 simple one-parameter read tool the description is mostly sufficient, and enumerating return fields compensates for the missing output schema. The absence of any failure-mode or configuration-prerequisite note leaves a real gap given zero annotations.

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% with a single well-described project_id, and the phrase 'for the project' only confirms the scoping the schema already states. No added format, default, or error semantics 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 gives a specific verb (Get) and an enumerated resource (comfy_dir, models_dir, custom_nodes_dir, active API URL) scoped to a project. The get/set contrast with cineflow_comfy_config_set is implicit in the name rather than stated, 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 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 the config_set sibling or any other environment-check tool, and no preconditions (e.g. project must be initialized). The agent must infer from the name that this is the read half of a get/set pair.

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