Skip to main content
Glama

estimate_video

Read-only

Estimate video generation costs before generation, compare models by length, resolution, and aspect ratio, and check remaining budget and duplicate requests.

Instructions

과금 없이 비용을 견적한다. 조건(길이·해상도·화면 비율)에 맞는 모델을 싼 순서로, 남은 예산과 함께 돌려준다.

    generate_video 를 부르기 전에 모델을 고르거나 예산이 충분한지 볼 때 쓴다. cheapest 는 예산 안에서 가장 싼 모델.
    조건을 지정하지 않으면 모델별 가장 싼 값을 가정한다. 조건을 만족하지 못하는 모델은 unavailable 에 이유와 함께 나온다.
    prompt 를 주면 같은 요청이 최근에 있었는지(duplicate_of)도 알려 준다.
    

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

Input Schema

NameRequiredDescriptionDefault
modelNo
promptNo
resolutionNo
aspect_ratioNo
duration_secNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavior beyond that: no billing occurs, results are ordered by price, unsatisfiable models are listed under `unavailable` with reasons, and duplicate_of is surfaced when a prompt is supplied. It does not discuss caching or the freshness of the budget figure, which keeps it short of a 5.

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?

Four short lines, front-loaded with the no-billing promise, then usage, then edge-case behavior. Every sentence introduces new information with no repetition of the name or schema.

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

Completeness5/5

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

For a five-parameter estimator with an output schema, this is complete: usage, defaults, failure handling (unavailable with reasons) and the cheapest alias are all explained, so an agent needs nothing else to call it correctly or interpret the response.

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?

With 0% schema coverage and no enums, the description carries the full burden and does so well: it maps the condition parameters to length, resolution and aspect ratio, explains that omitted conditions fall back to each model's cheapest value, and assigns prompt a duplicate-detection role. The model parameter itself is only implicitly explained (pass to pin a model), so it is not a 5.

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 concrete verb and resource — estimate cost with no billing — plus the exact return shape (models matching length/resolution/aspect ratio, sorted cheapest-first, with remaining budget). An agent can distinguish it from generate_video and list_models without opening a schema.

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?

Explicitly says to call it before generate_video when choosing a model or checking budget sufficiency, naming the sibling it precedes. It also scopes the prompt parameter to a duplicate-request check, so each usage mode has a stated trigger.

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