Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

shot.compile_prompt

Preview exactly what would be sent to the generation model for a shot — compiled prompt, reference images and videos, duration and cost. ignoredReferenceVideos counts the shot's reference videos the model won't receive; referenceVideoMode is follow or edit; problem says why shot.generate_video would refuse. Free.

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": {
      "shotId": "<shotId>",
      "target": "<target>"
    },
    "name": "shot.compile_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
shotIdYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behavioral burden and does well: it discloses that this is a preview, that it returns compiled prompt, reference images/videos, duration, and cost, and that it explains why shot.generate_video would refuse. It also clarifies fields like ignoredReferenceVideos and referenceVideoMode. It does not explicitly say no state is changed or mention permissions, but 'Preview' and 'Free' cover the main behavioral concerns.

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?

The description is front-loaded with the core purpose and remains compact: one sentence for the preview contents, then a dense clause covering ignoredReferenceVideos, referenceVideoMode, the problem field, and cost. Every sentence adds useful information and there is no filler.

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?

There is no output schema, and the description does a good job explaining the returned preview contents and key output fields. However, for a tool with three parameters at 0% schema description coverage, it leaves input semantics entirely unexplained, making the definition incomplete for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% for all three parameters, and the description does not explain shotId, the target enum values keyframe versus video, or the optional model parameter. It describes output fields instead, so it does not compensate for the undocumented input schema.

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?

The description states a specific verb and resource: previewing exactly what would be sent to the generation model for a shot, including compiled prompt, reference media, duration, and cost. It distinguishes the tool from shot.generate_video by explaining that it reports why shot.generate_video would refuse, so an agent can tell the preview/diagnostic tool apart from the generation tool.

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

Usage Guidelines4/5

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

The description gives clear context: use this to preview and diagnose what shot.generate_video would receive, and it notes the call is free. It does not explicitly state when not to use it or name all alternatives, but the preview-before-generation use case is strongly implied.

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

All CutClip.one 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