Skip to main content
Glama

Squall Studio

by com.squallstudio
OverviewDiscussionsAdmin

Attach continuity reference

attach_shot_continuity_reference

Attach an image that already exists in this project to a shot as a continuity reference. A continuity reference is fed into this shot's next clip generation as a layout, prop, wardrobe and screen-direction guide — it is NOT used as the shot's opening frame or exact composition. Attaching one changes nothing until the clip is generated again. Find asset ids with get_asset_library. A shot's own thumbnail is its clip's last frame, so attaching the previous scene's thumbnail is the cheapest way to carry continuity forward. To use an image that is not yet an asset here, use upload_shot_continuity_reference instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shot_idYesShot id (episode_shots row) to attach the reference to.
asset_idYesId of an existing image asset in this project.
guidanceNoHow the video model should use this reference, e.g. which positions or props to match and what to ignore. Saved on the reference and sent with every later generation of the shot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / guidance
      Added value: +{
+  "description": "How the video model should use this reference, e.g. which positions or props to match and what to ignore. Saved on the reference and sent with every later generation of the shot.",
+  "maxLength": 1000,
+  "type": "string"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries the behavioral burden. It explains that attaching changes nothing until the clip is regenerated, that the reference is only a guide, and that it does not set the opening frame. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, with the core action front-loaded and each subsequent sentence adding essential context: constraints, side effects, asset sourcing, and an alternative. There is no filler or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with no output schema, the description covers prerequisites, behavioral effect, timing, and the alternative path. The shot_id source is already indicated in the schema and the sibling tool list, making this complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter descriptions are already solid, so the baseline is 3. The description adds operational value by telling the agent how to source asset_id (get_asset_library) and recommending a specific asset choice, going slightly beyond schema field documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('attach') and resource ('an existing image in this project to a shot'), and clearly distinguishes itself from upload_shot_continuity_reference by limiting it to images that are already assets. It also clarifies what the reference is NOT used for, removing ambiguity.

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

Usage Guidelines5/5

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

Explicitly tells the agent to find asset IDs with get_asset_library, suggests a concrete cheap strategy (attaching the previous scene's thumbnail), and names upload_shot_continuity_reference as the alternative when the image is not yet an asset. This is strong when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Squall Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources