Skip to main content
Glama

Estimate credit cost

estimate_cost
Read-onlyIdempotent

Price a generation before starting it: the credits this model would charge for these options, and whether the current balance covers it. Uses the same validation and price calculation as generate_3d and generate, so for a valid request the figure is exactly what is charged. Omit scene to price every scene of the model. Nothing is charged and nothing is started.

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

Input Schema

NameRequiredDescriptionDefault
modelYesA model id from list_models.
sceneNoA scene id from list_models, e.g. 'image-to-3d'.
promptNo
optionsNoThe options you intend to pass; they change the price.

Output Schema

NameRequiredDescriptionDefault
modelYes
quotesYes
balanceYesCredits the account holds now.
availableYes
media_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • removedOutput schema / properties / quotes / items / properties / input_issue / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / quotes / items / properties / input_issue / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. First observed

TDQS

A4.4/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 bar is lower. The description still adds real value: 'Nothing is charged and nothing is started' reassures on side effects, and the claim that it reuses the same validation and price calculation as generate_3d/generate tells the agent the returned figure is authoritative rather than an approximation.

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 sentences, front-loaded with purpose and output, then accuracy guarantee, then the scene-omission rule and the no-side-effect guarantee. No filler and nothing repeated from the schema unnecessarily.

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?

An output schema exists, so return shape need not be described, and the description covers purpose, accuracy, side effects and the scene-omission behavior. It leaves the prompt parameter unaddressed and does not say what happens on an invalid request (only 'for a valid request'), a small completeness gap.

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?

Schema coverage is 75%, so the schema carries most parameter documentation. The description adds meaning the schema does not: omitting scene prices every scene of the model (schema only says it is a scene id), and that options are the ones you intend to pass because they change the price. The prompt parameter is unexplained in both, a minor gap.

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 and resource ('Price a generation before starting it') and enumerates the two outputs: credits the model would charge and whether the balance covers it. It is clearly distinguishable from generate/generate_3d, which it references as sharing the same calculation.

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?

The usage context is explicit — call this before starting a generation to preview cost and balance coverage — and it names generate and generate_3d as the tools whose charge it mirrors. It stops short of an explicit 'do not use this to actually start a job' or a pointer to get_balance for balance-only checks, so alternatives are implied rather than fully routed.

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