Skip to main content
Glama

Image To Image Price

image_to_image_price

Estimate image-to-image transformation cost by passing the same model, quality, and source image size the edit job will use. This prevents quotes that do not match the final charge.

Instructions

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.

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. First observedv0.6.3

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it warns that `quality` and the input size change the charge on some models, and that an incomplete quote may not match the job. It omits whether the call is free/non-mutating or any rate-limit behavior, but the key pricing-sensitivity trait is disclosed.

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 sentences, front-loaded with the purpose followed by the operational caveat about missing parameters. Nothing is wasted and the most important warning comes last in a short, scannable block.

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?

For a 12-parameter pricing tool with an output schema and full schema coverage, the description covers the one thing structured fields cannot: that a quote must mirror the upcoming job's parameters to be accurate. It could note that non-pricing parameters (seed, steps) do not affect the charge, but that gap is minor.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents that quality tiers 'differ sharply in price' and that image size affects pricing. The description reinforces which parameters matter for accuracy, but adds no syntax or semantics beyond what the schema provides, so the baseline of 3 applies.

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?

The description states a specific verb and resource: 'Calculate price for image-to-image transformation.' That distinguishes it from the actual edit operation, which it references as 'the edit call.' It does not name the sibling image_to_image directly, so differentiation is implicit rather than explicit.

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?

It gives concrete when-to-use guidance: call this with the same parameters and source image(s) the edit job will use, so the quote matches the job. It does not explicitly route the agent between this tool and the non-price siblings or state prerequisites, but the intended workflow is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.