Skip to main content
Glama

Estimate cost

estimate_cost
Read-onlyIdempotent

What a video or image would cost in credits, and whether the balance covers it. Spends nothing.

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": {
      "prompt": "<prompt>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoQuality tier: quick (cheapest), great (best value, default), cinema (most realistic). Or give `model` instead.
typeNoDefault video.
modelNoA model id from list_models, instead of a tier.
soundNoVideos: sound on or off, where the model has a switch.
promptYesWhat to make, in plain words. @handles use the person's saved characters.
durationNoSeconds (videos).
num_imagesNoImages per request (images).
resolutionNoe.g. "720p" or "1080p" for videos, "2K" for images. Defaults to the tier's.
with_imageNoPrice it as if a start image were attached.
aspect_ratioNoAspect ratio, e.g. "16:9", "9:16" (vertical, for Reels and TikTok) or "1:1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, so the description's bar is lower. The description adds useful behavioral context by saying it returns credit cost and balance sufficiency, and by reinforcing that it spends nothing.

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?

The description is two compact sentences with no filler. The core purpose and the no-cost guarantee are front-loaded.

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?

Given the rich input schema and strong annotations, the description covers enough for an agent to understand the tool's purpose and output intent. It could be stronger by explicitly linking itself to preflight use before creation tools, but it is otherwise complete.

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 input schema already documents all 10 parameters. The description does not add meaning about tier, model, duration, or other parameter interactions beyond what the schema provides.

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 states a specific purpose: estimating credit cost for a video or image and whether the balance covers it. It is clear enough to distinguish from creation tools, but it does not explicitly name alternatives such as create_video or get_balance.

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

Usage Guidelines3/5

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

Usage is implied as a preflight pricing check, especially through 'Spends nothing', but there is no explicit when-to-use guidance or comparison to sibling tools. An agent can infer the use case, but must reason about alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources