Skip to main content
Glama

estimate_video_cost

Calculate video generation costs based on duration, resolution, and audio settings to plan media production budgets.

Instructions

Estimate the cost of a video generation. Cost: $1.96 (Veo 3.1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationNoVideo duration in seconds
generate_audioNoWhether audio will be generated
resolutionNoVideo resolution. 1080p adds +33% cost720p

Implementation Reference

  • The handler function for estimate_video_cost tool which performs local cost calculation.
    def _handle_estimate_video_cost(arguments: Dict) -> Dict:
        """
        Handle estimate_video_cost tool call (Directive #242: Veo 3.1).
    
        Local calculation - no API call needed.
        """
        duration = arguments.get("duration", 8)
        generate_audio = arguments.get("generate_audio", True)
    
        # Validate duration (Veo 3.1: 4, 6, 8 seconds)
        if duration not in (4, 6, 8):
            duration = 8
    
        cost_table = VIDEO_COSTS_WITH_AUDIO if generate_audio else VIDEO_COSTS_NO_AUDIO
        cost = cost_table.get(duration, 4.80)
    
        return {
            "content": [{
                "type": "text",
                "text": f"Video Generation Cost: $1.96 USD (fixed price)\n\nProvider: Veo 3.1\nRequires: Tier 2+"
            }]
        }
  • The registration/dispatch logic that routes the estimate_video_cost tool call to its handler.
    if tool_name == "estimate_video_cost":
        return _handle_estimate_video_cost(arguments)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the cost ($1.96 for Veo 3.1) but doesn't explain what this tool actually does behaviorally - whether it performs calculations, looks up pricing, or returns static information. It doesn't disclose rate limits, authentication needs, or what happens when invoked.

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?

The description is extremely concise - just one sentence. While efficient, it may be too brief given the lack of annotations and sibling tool context. Every word earns its place, but more information might be warranted for this type of tool.

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

Completeness2/5

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

For a cost estimation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, how the cost calculation works, or what the $1.96 baseline represents. Given the complexity of cost estimation with multiple parameters and the lack of structured output documentation, more completeness is needed.

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 the schema already fully documents all three parameters. The description adds no parameter-specific information beyond what's in the schema. The baseline score of 3 reflects adequate but minimal value addition given the comprehensive schema documentation.

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?

The description clearly states the tool's purpose: estimating cost for video generation with a specific price point. It specifies the resource (video generation) and verb (estimate cost), but doesn't differentiate from sibling 'estimate_cost' or 'estimate_music_cost' tools, which appear to be similar estimation tools for different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'estimate_cost' or 'estimate_music_cost'. It doesn't mention prerequisites, limitations, or appropriate contexts for use. The only contextual information is the price point, which doesn't help with tool selection decisions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elestirelbilinc-sketch/vap-showcase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server