Skip to main content
Glama

Image To Image Price

image_to_image_price

Calculate price for image-to-image transformation.

Pass the same parameters and source image(s) the edit call will use: quality and the input size both change the charge on some models, so a quote without them may not match the job.


Available models:

  • Flux_2_Klein_4B_BF16: steps=4 (fixed), size=256-1536x256-1536, up to 3 input image(s), no negative_prompt

  • QwenImageEdit_Plus_NF4: steps=1-50 (default 40), size=256-1024x256-1024, output size = input size, up to 1 input image(s)

  • gpt-image-2.6 (test model): size=640-3840x640-3840, w/h rounded down to a multiple of 16, ≤8.29Mpx, side≤3840, aspect≤3, up to 5 input image(s), quality: low|medium|high|auto (default medium), no negative_prompt

  • nano-banana-2.1 (test model): size=352-11712x352-11712, w/h rounded down to a multiple of 16, ≤17.20Mpx, side≤11712, aspect≤8.4, up to 5 input image(s), no negative_prompt

  • gpt-image-2.5 (test model): size=640-3840x640-3840, w/h rounded down to a multiple of 16, ≤8.29Mpx, side≤3840, aspect≤3, up to 5 input image(s), quality: low|medium|high|auto (default high), no negative_prompt

  • gpt-image-2 (test model): size=512-2048x512-2048, output size = input size, up to 2 input image(s), quality: low|medium|high|auto (default medium), no negative_prompt

  • gpt-image-1.5 (test model): size=1024-1536x1024-1536, output size = input size, up to 2 input image(s), quality: low|medium|high (default medium), no negative_prompt Models marked (test model) are experimental: they may change or disappear. Prefer an unmarked model unless the caller asks for one of them.

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

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed the job will use
imageNoSource image (URL, data URI or base64). Some models price by its size, so pass the one the job will use
lorasNoLoRA adapters the job will use: [{'name': str, 'weight': float}]
modelYesAI model name
stepsNoNumber of diffusion steps. Limits per model (see the model list)
widthNoOutput width the job will use. Limits per model (see the model list)
heightNoOutput height the job will use. Limits per model (see the model list)
imagesNoSeveral source images, as the job will send them. Mutually exclusive with 'image'
promptYesTransformation description
qualityNoQuality tier, e.g. 'low', 'medium', 'high'. Tiers differ sharply in price, so omitting it can misquote badly
guidance_scaleNoGuidance the job will use. Defaults to the model's own value; limits per model (see the model list)
negative_promptNoThings to exclude — quote it if the job will use it

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / images / anyOf
      Previous value: -[
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {},
      +    "maxItems": 16,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a solid job: it discloses per-model step ranges, size/resolution and aspect limits, input-image caps, which models support quality tiers and their defaults, which forbid negative_prompt, and that 'test model' entries are experimental and may disappear. What it does not disclose is whether the call costs credits, rate limits, or what an invalid model/size does.

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

Conciseness4/5

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

Front-loaded with the one-line purpose and the critical 'pass the same parameters' instruction, then a rule-separated model catalog that is dense but earns its space. The catalog repeats constraint phrasing across the gpt-image entries, so it is longer than strictly necessary, but nothing is padding.

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?

Return values are covered by the output schema, so the description needn't explain them. For a 12-parameter pricing tool, the missing pieces an agent would need — per-model valid ranges, quality tiers, image count limits, experimental-model caveat — are all present, along with the aliasing rule that makes the quote accurate.

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

Parameters5/5

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

Schema coverage is 100% (baseline 3), but the description goes well beyond it: the schema's own parameter docs literally defer to 'see the model list', and the description supplies that list with per-model step, size, quality, aspect and input-image semantics. It also explains why quality and input size must match the real job to avoid a misquote, which is meaning the schema does not convey.

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?

Opens with a specific verb+resource: 'Calculate price for image-to-image transformation', which cleanly separates it from text_to_image_price, image_to_text_price and the other *_price siblings. It also frames itself as the quoting counterpart to the edit call ('the edit call will use'), though it never names that sibling (image_to_image) explicitly.

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?

Gives a clear usage rule: pass the same parameters and source image(s) the edit job will use, because quality and input size change the charge. It also adds a model-selection guideline ('Prefer an unmarked model unless the caller asks for one of them'). No explicit statement of when not to use it (e.g. after the job has already run) or of error conditions.

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.