Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venice Music Cost Quote

venice_audio_quote
Read-onlyIdempotent

Get a price quote for music generation before queuing to budget accurately; no authentication required.

Instructions

Get a price quote for a music generation BEFORE queuing. Useful for budgeting. No authentication required.

Input Schema

NameRequiredDescriptionDefault
modelYesMusic model id, e.g. "elevenlabs-music".
character_countNoRequired for character-based pricing models.
duration_secondsNoOptional duration in seconds as a positive integer or numeric string. Model-specific.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / duration_seconds / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9]\\d*$",
+    "type": "string"
+  }
+]
    • addedInput schema / properties / duration_seconds / description
      Added value: +"Optional duration in seconds as a positive integer or numeric string. Model-specific."
    • removedInput schema / properties / duration_seconds / maximum
      Removed value: -300
    • removedInput schema / properties / duration_seconds / minimum
      Removed value: -1
    • removedInput schema / properties / duration_seconds / type
      Removed value: -"number"
  2. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

Does 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 structurally. The description adds a genuinely useful behavioral fact not in the annotations — "No authentication required" — plus the pre-queue timing guarantee, though it says nothing about rate limits or quote validity windows.

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?

Three short sentences, front-loaded with the core action and scope; each sentence contributes (purpose, use case, auth precondition) with no redundancy.

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?

For a simple 3-param read-only quote tool with full schema coverage and annotations, this is nearly sufficient. The one minor gap is that no output schema exists and the description never indicates what the quote actually returns (e.g., cost amount, currency), leaving the agent to discover the response shape empirically.

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 100%, so model, character_count, and duration_seconds are all documented in the schema with their constraints. The description adds no parameter guidance beyond noting nothing about model-specific price dimensions, so baseline 3 applies.

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 specific verb (get a price quote), resource (music generation), and timing constraint (BEFORE queuing), which cleanly distinguishes it from the sibling venice_music_generate. An agent can tell immediately this is a pre-flight costing call, not a generation call.

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?

"BEFORE queuing" and "Useful for budgeting" give clear context for when to reach for this tool rather than the generator. No explicit when-not conditions or named alternatives (e.g., venice_video_quote for video), so it stops short of the top tier.

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