Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_cache_cleanup

Cleans temporary latents and preview cache from ComfyUI output directories to free SSD space.

Instructions

Clean up temporary latents in output/latents/ and preview cache (#608) to free SSD space.

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

Input Schema

NameRequiredDescriptionDefault
comfy_dirNoTarget ComfyUI directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 for a delete operation, and it falls short. It never says whether deletion is permanent, whether in-flight workflows holding those latents are affected, or whether there is a dry-run or confirmation step.

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 verb, targets, and benefit in order; nothing is padded. The issue-tracker reference "(#608)" is minor noise for an agent, but the sentence otherwise earns every word.

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?

The scope of what gets removed is specified at path level, which is the core of a cleanup tool. Against a destructive operation with no annotations and no output schema, however, it should still say whether deletion is recoverable and whether it is safe mid-run.

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?

There is only one optional parameter and schema coverage is 100%, so the schema already explains comfy_dir. The description adds no meaning about how the directory influences the cleanup targets, which is acceptable given the schema does the work.

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 ("clean up") plus concrete resources ("temporary latents in output/latents/ and preview cache") and a stated goal ("free SSD space"). It clearly does not overlap any sibling, although it never names a sibling to differentiate itself from.

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

Usage Guidelines3/5

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

The stated goal of freeing SSD space implies when to reach for it, but there is no explicit trigger, no prerequisites, and no when-not-to-use guidance (e.g., while a generation job is running). Usage is inferred rather than instructed.

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