Skip to main content
Glama

Estimate cost

estimate_cost
Read-only

Price a generation before running it. Asks Higgsfield for an exact figure per format and falls back to a labelled best guess where it can't. Also validates the request. 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": {
      "brief": "<brief>",
      "formats": "<formats>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoimage
brandNoThe full brand, only when there is no kit for it. brand_id is simpler.
briefYes
cropsNoStarting crop per format for master sizing, e.g. {"9:16": {"x": 0.4, "y": 0.5}}. Change it later with compose_asset at no cost.
modelNoDefaults: recraft-v4.1 for image, kling-3-std for video. See list_models.
videoNo
sizingNoImages only. master: one render at the native ratio that best covers every format, each format cropped from it (one charge, identical picture in every size). separate: one render per format. Video always renders per format.master
formatsYesSocial formats, see list_formats
overlayNo
brand_idNoA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.
preset_idNoMarketing Studio preset from list_marketing_presets. Needs 1 or 2 references.
referencesNoProduct images or app screenshots for marketing-studio-2 and marketing-studio-flare: public https URLs, studio file paths (uploads/...), or asset ids from the brand kit (get_brand). Product first.
green_screenNoFor a lifestyle shot of someone using the app: the phone or tablet screen comes out plain bright green, so place_screen can put the real app on it (on the still, or on every frame after animate_image). Describe the camera behind the person (seen from behind their shoulder, looking down at the phone), so the screen can face both them and the viewer; then review_shot the result.
text_overlayNoBake headline, CTA and logo on afterwards in brand fonts (recommended; models misspell text)
negative_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safe/no-side-effect profile (readOnlyHint, openWorldHint), and the description adds real behavior on top: it queries an external pricing source, degrades to a labelled fallback estimate when no exact figure exists, validates the request, and incurs no cost. It even sketches the return shape (a figure per format). The main omission is what happens when validation fails (error vs. partial estimate).

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 sentences, front-loaded with the core purpose, then what it does mechanically, then the reassuring cost constraint. No filler and no repetition of the title or schema.

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

Completeness3/5

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

For a 15-parameter tool with deep nested objects (brand, brief, crops, video) and no output schema, the description explains the core mechanic and the fallback behavior but leaves the pricing-relevant parameters and the validation-failure outcome unexplained. It is adequate as a summary but thin relative to the schema's complexity.

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?

With 15 parameters and only 67% schema description coverage, the description should carry some of the load, but it names no parameter at all — not mode, formats, model, sizing, or video duration — the exact inputs that drive the price. "Per format" loosely gestures at the formats array, but nothing explains which knobs change the estimate, which is the single most valuable thing this description could add.

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?

"Price a generation before running it" gives a specific verb (price) and resource (a generation) and makes the pre-execution scope explicit. It implicitly separates itself from the generation siblings ("before running it", "Spends nothing") without naming them, so an agent can distinguish it from generate_assets by inference rather than by direct reference.

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 description supplies a clear usage context: call this before actually running a generation, and it doubles as a request validator. That is enough to know when to reach for it. It stops short of a 5 because it names no alternative path and gives no when-not case (for example, whether to call it repeatedly or cache the estimate).

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