Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_assets_transfer

Transfer and clone characters, locations, and props from a source project into a target project, copying turnaround cards, plates, and voice models while preserving project.json continuity.

Instructions

Transfer and clone characters, locations, or props from an existing project into the current target project. Automatically copies turnaround cards, plates, and voice models into target materials while maintaining project.json continuity.

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": {
      "source_project": "<source_project>",
      "target_project_id": "<target_project_id>"
    },
    "name": "cineflow_assets_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNoOptional specific character or location names to transfer (e.g. ['Мартин', 'Лиза']).
asset_typesNoTypes of assets to transfer. Defaults to all available.
source_projectYesSource project ID or title query (e.g. 'Убийство' or 'p_murder_mystery').
conflict_strategyNoHow to handle naming conflicts with existing assets in target project. Defaults to 'skip'.
target_project_idYesTarget project ID receiving the assets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden, and it does add real value beyond the schema by naming the concrete artifacts copied ('turnaround cards, plates, and voice models into target materials') and the state effect ('maintaining project.json continuity'). It stops short of stating whether target assets are mutated destructively, whether the operation is reversible, or what happens on partial failure.

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?

Two sentences, no filler, with the core action and scope front-loaded before the side-effect detail. The second sentence is dense but every clause carries information; only minor tightening is possible.

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 five-parameter mutation tool with no annotations and no output schema, the definition covers what the tool does and what it copies, which is the critical part. It leaves gaps on the result surface (what the caller gets back, e.g. counts or per-asset status) and on failure/conflict behavior, which the description should cover since no output schema exists to do so.

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 all five parameters, including the enum for asset_types and conflict_strategy, are documented in the schema itself, so the baseline is 3. The description echoes the character/location/prop vocabulary but adds no new meaning, such as how conflict_strategy values behave in practice.

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 opens with a specific verb and resource ('Transfer and clone characters, locations, or props') and scopes it explicitly to moving assets from a source project into the target project. This is unambiguous against the sibling catalog, none of which appear to move assets between projects, though no sibling is named as a contrast.

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?

Usage is only implied: the phrase 'from an existing project into the current target project' tells an agent this is a cross-project operation rather than an in-project edit, which is likely enough to distinguish it from project_create or materials_attach. There is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g. whether the target project must already exist or be initialized).

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