Skip to main content
Glama

Kubeez

estimate

Read-onlyIdempotent

Scope: none (any authenticated key). Preview BOTH the credit cost AND the processing time of a generation WITHOUT deducting credits.

PRE-FETCH (mandatory): resources/read kubeez://skills/billing-confirmation — Kubeez has NO refunds. The skill explains when a preview is mandatory vs optional and how to phrase the confirmation.

Pass the same model_id you'd pass to generate_media / generate_music.

Resolution-priced image models (gpt-image-2, gpt-image-2-5-flare, gpt-image-2-5-sunburst, gpt-image-2-6-flare, gpt-image-2-6-sunburst, nano-banana-2, nano-banana-2-1, nano-banana-pro, flux-3-klein, seedream-5-5): pass the same resolution ('1K' default, '2K', '4K'; seedream-5-5 takes '1.5K' default or '2K') and generation_type you will pass to generate_media; each tier has its own price. FLUX 3 Klein is a flat-priced IMAGE model (not the per-second FLUX 3 video family): pass generation_type='image-to-image' when images will be attached, since editing is priced on its own. P-Video: pass the same quality ('720p', '1080p', or a '-draft' tier). Kling 3.0 Omni: pass reference_video_seconds whenever a clip is attached; the clip picks the billed lane (References with a clip bills its dearer -video tier, no clip runs on Frames). A References clip alone bills the clip's length; with stills beside the clip it bills the duration you pick, so also pass generation_type='image-to-image' and that duration. Kling 4.0: pass reference_video_seconds (total of the reference clips) and the same elements you will pass to generate_media; a video element moves the quote onto the -video row and adds its seconds, measured by the server (it must be a Kubeez upload). Reference clips plus video elements over 30s combined are refused. Kling 4.0 Flash (kling-4-0-flash-720p) quotes the same way with a 20s combined cap; a Flash run with first_frame_url bills the no-clip row, so quote it without reference_video_seconds. Gemini Omni 1.2 Flash (gemini-omni-1-2-flash-*): pass duration for a text, image or frames run; for a video edit pass reference_video_seconds (the clip's length is the bill) or video_edit=true, which without a length quotes the 15s maximum. GPT Image 2.6 (gpt-image-2-6-economy / -flare / -sunburst): pass reference_image_count, the number of image URLs you will send in source_media_urls (duplicates count). Any count above 0 quotes the edit, which on Flare and Sunburst adds a charge per reference image; the explanation shows base + per image x count. An edit quoted without a count assumes the 16-image maximum (pessimistic). Seedream 5.5 (seedream-5-5, resolution '1.5K' or '2K'): pass reference_image_count the same way; every reference image adds its charge, the first one included, and an edit quoted without a count assumes the 10-image maximum (pessimistic). Seedream 5.0 Pro (seedream-5-pro, -edit, -2K, -edit-2K): pass reference_image_count too; the first reference image is free and every one after it adds a charge, and an edit quoted without a count assumes the 10-image maximum (pessimistic). For an animated GIF pass output_format='gif' and the same frame_count / frame_duration_ms you will pass to generate_media: GIF is text-to-image only and has its own price by frame count, not by resolution.

Per-duration video models — pass duration (seconds). Audio defaults to ON across all video models (matches generate_media's default). For Kling 3.0 this means the per-second audio surcharge (rate in get_models — don't assume) is reflected by default; pass sound=false to preview the silent rate. For Seedance 2 audio is free (same rate either way). Seedance 2 with video reference — pass reference_video_seconds (from get_upload_session.media[].duration_seconds; omitted, the quote assumes the 15s cap). P-Video with audio input — pass reference_audio_seconds. These seconds only shape the QUOTE: generate_media always bills the server's measurement of the attached file.

Returns: • credits: { estimated_credits, mode, rate_per_second?, explanation, pessimistic } • time: { estimated_seconds, source } • price_for: seconds → the COMPLETE credit cost at that length, for THIS model, when it supports more than one. Offer the user the other lengths instead of silently keeping yours — duration is the biggest lever on a per-second bill. In agent-chat, pass these straight to show_plan_card as duration_options and the card renders tappable length chips. When credits.pessimistic is true the quote assumed a ceiling and the real bill may be lower: pass the file's measured seconds (get_upload_session.media[].duration_seconds) and re-estimate.

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

Input Schema

NameRequiredDescriptionDefault
modelYes
soundNo
promptNo
qualityNo
durationNo5
elementsNo
resolutionNo
video_editNo
frame_countNo
output_formatNo
variant_countNo
generation_typeNotext-to-image
negative_promptNo
frame_duration_msNo
reference_image_countNo
reference_audio_secondsNo
reference_video_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial behavior: no refunds exist, no credits are deducted, quotes may be pessimistic because ceilings are assumed, and server-measured seconds override quoted seconds at billing time. These are the risk-relevant facts an agent needs before promising a price to a user.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening scope line and the Returns block are well front-loaded, but the middle is a dense block of per-model quoting rules (Kling 3.0/4.0/Flash, Seedream, GPT Image, Gemini Omni, P-Video, GIF) that reads like documentation. Much of that model-specific logic duplicates what the mandated billing-confirmation skill presumably covers, so the length is only partly earning its place.

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 17-parameter pricing tool with an output schema and rich annotations, the description leaves nothing an agent needs unresolved: it explains the pessimistic flag, the price_for duration options, and how to hand options to show_plan_card. Return-value explanation is a bonus since the output schema already exists.

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 description coverage across 17 params, the description carries the full load and does most of it: it gives conditional semantics for resolution tiers, generation_type, sound, duration, elements, reference_video_seconds, reference_image_count, reference_audio_seconds, output_format, frame_count, frame_duration_ms, and video_edit. The gap is that prompt, negative_prompt, and especially variant_count (which likely multiplies cost) are never explained.

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: preview credit cost AND processing time without deducting credits. It immediately distinguishes itself from generate_media by noting it is a preview that charges nothing, and it names the sibling whose model_id must be mirrored.

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 routes usage: a mandatory pre-fetch of the billing-confirmation skill, the instruction to pass the same arguments that will later go to generate_media, and guidance to offer alternative durations rather than silently keeping one. It also tells the agent to re-estimate when credits.pessimistic is true, which is a concrete when-to-call-again rule.

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