Skip to main content
Glama
seocombat

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Quote a clip

quote_video
Read-only

Price a video generation before spending credits: retrieve the credit cost, output dimensions, and warnings so users can approve the cost before rendering.

Instructions

Price one generate_video call WITHOUT spending credits: its credits (unit_credits per second of duration_s), its width and height, and warnings. Always call this first and show the user the price before generate_video. A reference is {upload_id, rights_confirmed: true} for a picture from upload_image or create_upload (rights_confirmed states you may use the people and works in it), {run_id} of a succeeded generate_image run of this account until its reusable_until, or {asset_id} of a picture asset from create_asset, whose rights were confirmed when it was made. A generation that fails is charged nothing. An identical request returns the same run it started before, so a call repeated after a lost answer starts nothing new; to make another one with the same request on purpose, pass attempt 2. While generations are closed it answers generations_disabled or generations_marking_pending and charges nothing.

Input Schema

NameRequiredDescriptionDefault
modeYes
modelYes
cameraNo
promptYes
duration_sYes
last_frameNo
referencesNo
resolutionYes
first_frameNo
aspect_ratioYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.34.0
    • addedInput schema / properties / camera
      Added value: +{
+  "enum": [
+    "static",
+    "push_in",
+    "pull_back",
+    "pan"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "seedance-2.0",
-  "seedance-2.0-mini",
-  "seedance-2.0-fast",
-  "seedance-2.5"
-]New value: +[
+  "seedance-2.0",
+  "seedance-2.0-mini",
+  "seedance-2.0-fast",
+  "seedance-2.5",
+  "kling-3.0",
+  "gemini-omni-flash-1.1"
+]
    • changedInput schema / properties / resolution / enum
      Previous value: -[
-  "480p",
-  "720p",
-  "1080p"
-]New value: +[
+  "360p",
+  "480p",
+  "720p",
+  "1080p"
+]
  2. Addedv0.33.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial context beyond readOnlyHint=true/destructiveHint=false: no credits consumed, failed generations are free, and the generations_disabled / generations_marking_pending answers. However, the idempotency and "pass attempt 2" sentences describe generate_video semantics rather than a read-only pricing call, which muddies the side-effect picture and risks the agent believing quoting can start a run.

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

Conciseness3/5

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

Front-loaded well, opening with the value proposition and the call-ordering rule in the first two sentences. The back half drifts into generate_video's retry and idempotency behavior, which does not belong in a pricing tool's description and competes for attention with the reference-shape guidance that actually matters here.

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

Completeness4/5

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

With no output schema and zero schema text, the description does the heavy lifting: it names what comes back (credits as unit_credits per second of duration_s, width, height, warnings) and enumerates the reference provenance needed to build a valid call. Gaps remain on how model/mode/resolution choices affect the quoted price, which is the core reason an agent would call this tool.

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 0% across 10 parameters, and the description earns real credit for the `references` / `first_frame` shape: it explains the three accepted variants, their provenance (upload_image, create_upload, a succeeded generate_image run until reusable_until, create_asset) and the meaning of rights_confirmed. But required parameters that drive the price itself — mode, model, resolution, aspect_ratio, duration_s — get no semantic treatment, and it references an `attempt` parameter that does not exist in the 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?

States a concrete verb and resource ("price one generate_video call") and immediately disambiguates from the sibling that actually spends credits with "WITHOUT spending credits". The contrast with generate_video makes the tool's role unmistakable without opening a schema.

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?

Gives an explicit ordering directive: "Always call this first and show the user the price before generate_video." It also names the exact trigger for the related pricing siblings by scoping itself to generate_video, and it covers the blocked state ("while generations are closed") so the agent knows quoting still works when generation does not.

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