Skip to main content
Glama

Quote an AI motion clip

quote_motion_clip
Read-onlyIdempotent

The exact credit price of ONE prompt-to-motion clip (generate_motion_clip) BEFORE it is made, and whether this account may start it right now. Read-only: nothing is created, reserved or charged, and no prompt is checked. Returns credits (5 s = 115), the balance, canAfford, canStart and, when it cannot be started, blockedBy (code + message) and a nextAction. The price is the account's own: 115 at the standard price, 50 at the low price, which applies for the credits bought in the last 31 days (an active paid plan period or a credit pack). lowPriceCreditsLeft says how many low-price credits are left; priceWithRecentPayment is present when this quote is at the standard price. Too few credits, clips already in flight and the daily limit show up here. Tell the user the price before you call generate_motion_clip. (quote_video is the other quote: animated scenes of a normal video.) Requires the "video:read" scope. Optional tier: "seedance-2.5-480p" (Seedance 2.5 480p (with sound), 4-30 s, 68 credits per second: 5 s = 340, 15 s = 1020; 30 per second at the low price); "seedance-2.5-720p" (Seedance 2.5 720p (with sound), 4-30 s, 152 credits per second: 5 s = 760, 15 s = 2280; 66 per second at the low price); "wan-3.0-480p" (Wan 3.0 480p (with sound), 2-30 s, 33 credits per second: 5 s = 165, 15 s = 495; 15 per second at the low price); "wan-3.0-720p" (Wan 3.0 720p (with sound), 2-30 s, 66 credits per second: 5 s = 330, 15 s = 990; 29 per second at the low price); "wan-3.0-1080p" (Wan 3.0 1080p (with sound), 2-30 s, 131 credits per second: 5 s = 655, 15 s = 1965; 57 per second at the low price). A tier with sound returns the clip WITH an AI-generated sound track (speech, ambience) and the "no spoken dialogue" suffix is not added. Lip-sync, face swaps and talking avatars (a person talking to the camera) stay refused on every tier, with or without sound. A clip on an optional tier can take up to 30 minutes: keep polling, the credits stay held while it is being made. Without tier the clip is the standard silent one described above. approxUsd is the same price in USD at what a credit costs this account, and approxUsdBasis says how it is worked out.

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": "quote_motion_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoOptional. A higher-quality model with sound: seedance-2.5-480p = Seedance 2.5 480p (with sound); seedance-2.5-720p = Seedance 2.5 720p (with sound); wan-3.0-480p = Wan 3.0 480p (with sound); wan-3.0-720p = Wan 3.0 720p (with sound); wan-3.0-1080p = Wan 3.0 1080p (with sound). Omit it (or pass seedance-2.0-mini-480p) for the standard silent clip. A tier with sound costs more per second: quote it first.
durationNoClip length in whole seconds (default 5). Up to 12 without tier; up to 30 with an optional tier. From 4 without tier; from 2 on a tier that makes shorter clips.
aspect_ratioNoFrame shape (default 9:16).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, and the description reinforces this with 'nothing is created, reserved or charged, and no prompt is checked' — the specific thing an agent would worry about for a cost tool. It goes further than the annotations by disclosing the auth scope ('video:read'), that failures surface as blockedBy codes, that tier clips can take up to 30 minutes with credits held, and the low-price/31-day credit rule. Deduction only because a few details (e.g. exact blockedBy codes) are alluded to rather than enumerated.

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-loading is excellent — the first two clauses state price and read-only status before any detail. But the body is a single dense paragraph with a long parenthetical tier block that repeats the model name and 'with sound' phrasing five times, and some pricing numbers appear in both the prose and the tier list. It is informative but longer than a 3-parameter tool warrants, and would benefit from the tier pricing being split out or omitted as duplicated schema metadata.

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, the description correctly carries the return-shape burden, enumerating credits, balance, canAfford, canStart, blockedBy, nextAction, approxUsd and approxUsdBasis. The remaining omissions are small: it does not say what nextAction contains semantically, and the seedance-2.0-mini-480p path is left unexplained. Overall complete enough to call blind.

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%, so 3 is the floor; the description earns above that by attaching concrete cost consequences to each tier ('68 credits per second: 5 s = 340') and their low-price rates, which the schema does not provide. It also explains the default and silent behavior when tier is omitted, plus the duration bounds per tier ('up to 12 without tier; up to 30 with an optional tier'). Minor gap: the seedance-2.0-mini-480p enum value the schema mentions is never addressed in the prose, and the enum tier block is hard to map back to prices.

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?

Names a specific verb and resource ('The exact credit price of ONE prompt-to-motion clip ... BEFORE it is made') plus the precise state check ('whether this account may start it right now'). It explicitly distinguishes itself from both siblings, naming generate_motion_clip as the action it precedes and quote_video as 'the other quote' for a different asset type.

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 call-order instruction: 'Tell the user the price before you call generate_motion_clip.' It also tells the agent when to reach for the sibling ('quote_video is the other quote: animated scenes of a normal video') and what to do when the result is blocked (blockedBy plus a nextAction).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources