Skip to main content
Glama

Quote the credit price of a video

autoshort_quote_video
Read-onlyIdempotent

Get the exact credit price for a video before creating it. Check account eligibility, balance coverage, and daily spending cap at no charge.

Instructions

The exact credit price of a video BEFORE it is made. Read-only: nothing is created, reserved or charged. Tell the user the price, then call the creating tool. mode "motion_clip": one moving clip from a prompt (autoshort_generate_motion_clip), by duration and resolution; also says whether this account can start it now (canStart, blockedBy). mode "stills": a normal narrated video made of still images (autoshort_generate_chat_video, or tool "autoshort_generate_video"). Also returns the balance, whether it covers the price, and this key's remaining daily spending cap. 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": {
      "mode": "<mode>"
    },
    "name": "autoshort_quote_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesWhat to price.
toolNostills only: which tool to price (default autoshort_generate_chat_video).
durationNoSeconds: the clip length (motion_clip, 4-12) or the video length (stills, 8-90).
resolutionNomotion_clip only: the default is 480p.
aspect_ratioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description restates them ("Read-only: nothing is created, reserved or charged"), though the "reserved or charged" and "Free" details add some value. More useful is the disclosure of what comes back: the balance, whether it covers the price, the key's remaining daily cap, plus canStart/blockedBy. No mention of failure modes or what happens for invalid durations/resolutions per mode.

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?

Front-loads the core value (exact price before creation), then the safety statement, then the workflow, then mode breakdown — a sensible order with little waste. Some phrasing is compressed to the point of choppiness ("Free.", parenthetical tool names), but no sentence is filler.

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 five parameters, the description does the necessary lifting by naming the returned fields (price, balance, coverage, daily cap, canStart/blockedBy) so an agent knows what to report. For a read-only quoting tool this is close to complete; the gaps are aspect_ratio's meaning and behavior on invalid inputs.

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 coverage is 80%, so the schema already carries most parameter meaning; the description reinforces mode semantics and explains that 'tool' applies to stills only, which matches the schema. However, aspect_ratio is undocumented in both schema and description, and duration semantics (4-12 vs 8-90) are already in the schema rather than added to here. A baseline 3 reflects modest added meaning.

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?

States a specific verb and resource: returns the exact credit price of a video before generation, and breaks that down by mode ("motion_clip" vs "stills"). It also names the creating tools each mode prices, which helps an agent connect quote to generate. It does not differentiate itself from the sibling autoshort_estimate_cost or autoshort_get_credit_balance, so it stops short of full sibling disambiguation.

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?

Gives a clear workflow instruction: quote the price, tell the user, then call the creating tool, and states which creating tool applies to each mode. It also notes the motion_clip mode reports canStart/blockedBy so the agent knows whether generation can proceed. Missing is explicit when-not guidance relative to the other cost/balance siblings.

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