venice_video_quoteGet a video generation price quote before queuing, with no authentication required. Provide model and duration to check cost upfront.
Get a price quote for a video generation BEFORE queuing. No authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | Video model id, e.g. "veo3.1-fast-text-to-video". | |
| duration | Yes | Duration as model-specific string enum, e.g. "4s", "6s", "8s". |
Changes observed during successful MCP inspections.
v0.3.0Input schema / requiredPrevious value: -[
- "model"
-]New value: +[
+ "model",
+ "duration"
+]v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds two genuinely useful facts beyond that: no authentication is required, and the call happens before queuing (so it does not consume/enqueue a job).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the core purpose and the pre-queue constraint. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter, read-only quote tool this is nearly complete. The one gap is that no output schema exists and the description does not hint at what the quote returns (e.g., credit/cost fields), which an agent may want to know before parsing the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both parameters (model, duration) are fully documented in the schema itself. The description adds no format, enum, or constraint detail beyond it, which is the correct baseline when the schema does the work.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (get a price quote) and resource (video generation), with the temporal qualifier 'BEFORE queuing' that separates it from venice_video_generate. The sibling venice_audio_quote confirms the quote-then-generate pattern, and this tool is clearly the video variant.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'BEFORE queuing' tells the agent this is a pre-flight step, which implies it should be called prior to venice_video_generate. It gives clear context but never names the alternative tool explicitly or states when a quote is unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.