Skip to main content
Glama

var2_estimate_cost

Read-only

Token-cost estimate for one or more planned create_* calls. Use when the user asks "how much".

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": {
      "items": "<items>"
    },
    "name": "var2_estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / items / properties / type / enum
      Previous value: -[
      -  "text-to-image",
      -  "image-to-image",
      -  "text-to-video",
      -  "image-to-video",
      -  "reference-to-video",
      -  "video-to-video",
      -  "audio-to-video",
      -  "create-music",
      -  "extend-music",
      -  "replace-music-section",
      -  "create-dialog",
      -  "image-to-3d",
      -  "upscale",
      -  "remove-bg",
      -  "draft-upgrade"
      -]New value: +[
      +  "text-to-image",
      +  "image-to-image",
      +  "text-to-video",
      +  "image-to-video",
      +  "reference-to-video",
      +  "video-to-video",
      +  "audio-to-video",
      +  "create-music",
      +  "cover-music",
      +  "extend-music",
      +  "replace-music-section",
      +  "create-dialog",
      +  "image-to-3d",
      +  "upscale",
      +  "remove-bg",
      +  "draft-upgrade"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / params / description
      Added value: +"Same params as the create/modify call. topaz-upscale: pass image_url (or input_width + input_height) and upscale_factor for an exact quote."
  3. Changed1 schema field changed
    • changedInput schema / properties / items / items / properties / type / enum
      Previous value: -[
      -  "text-to-image",
      -  "image-to-image",
      -  "text-to-video",
      -  "image-to-video",
      -  "reference-to-video",
      -  "video-to-video",
      -  "audio-to-video",
      -  "create-music",
      -  "extend-music",
      -  "replace-music-section",
      -  "create-dialog",
      -  "image-to-3d",
      -  "upscale",
      -  "remove-bg"
      -]New value: +[
      +  "text-to-image",
      +  "image-to-image",
      +  "text-to-video",
      +  "image-to-video",
      +  "reference-to-video",
      +  "video-to-video",
      +  "audio-to-video",
      +  "create-music",
      +  "extend-music",
      +  "replace-music-section",
      +  "create-dialog",
      +  "image-to-3d",
      +  "upscale",
      +  "remove-bg",
      +  "draft-upgrade"
      +]
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe, non-mutating operation. The description adds that the estimate is for planned create_* calls, implying a preflight quote, but it does not disclose estimate accuracy, whether the quote is binding, or the return format.

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?

Two short sentences, front-loaded with the core purpose and followed immediately by the usage trigger. There is no wasted text.

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 batch estimator with nested per-item fields and no output schema, the description is too sparse. It omits return shape/units, exactness caveats, and practical limits, leaving too much key context to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says items represent one or more planned create_* calls, which gives high-level meaning to the array. With 0% schema description coverage, however, it does not explain required model_id/type, quantity, max 50 items, or how params mirror create calls, so it does not compensate for the coverage gap.

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?

States the specific action (token-cost estimate) and target (one or more planned create_* calls), and includes the user trigger 'how much'. It implicitly distinguishes from create_* execution siblings but does not explicitly name an alternative or scope limitation.

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?

Explicitly says when to use it: when the user asks 'how much', and frames it for planned create_* calls. It lacks explicit when-not guidance or named alternatives beyond that trigger.

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