Skip to main content
Glama

gflow_upscale_image

Upscale a platform-generated Flow image to 2K or 4K and save it locally at no credit cost. Use it to raise image resolution when media_id and scale are known.

Instructions

Upscale a platform-generated Flow image to 2K or 4K and save it locally. media_id is the UUID of the image to upscale. scale is '2k' or '4k' (4k requires Ultra subscription; Pro/Plus accounts support 2k). project is optional (resolved from the local catalog when omitted). out_dir is the output directory (defaults to configured images directory; must resolve inside the configured output directory). profile selects the auth profile (defaults to the active profile). Spends no credits: image upscale is free.

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": {
      "media_id": "<media_id>"
    },
    "name": "gflow_upscale_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo2k
out_dirNo
profileNodefault
projectNo
media_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.83.0

TDQS

A4.5/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 it well: it discloses that no credits are spent, the tier gating on 4k, that project is resolved from a local catalog when omitted, and — importantly — that out_dir must resolve inside the configured output directory, a real security constraint. It stops short of saying what happens on an already-upscaled image, file naming, or overwrite behavior.

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?

Six tightly packed sentences, front-loaded with the action and outcome before per-parameter clauses. Every sentence adds information the schema or annotations do not carry; nothing is redundant.

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 5-parameter mutation-free tool with no annotations but an output schema, this covers the essentials: cost, tier gating, path safety, and all defaults. Minor gaps remain around error cases and the fate of the output file, but the agent has enough to call it correctly.

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 0%, so the description must compensate and it does for all five parameters. It gives media_id's type (UUID), supplies the allowed scale values with tier semantics that the schema does not enumerate, and explains the default/resolution behavior of project, out_dir, and profile.

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 ('Upscale a platform-generated Flow image'), the outcome ('to 2K or 4K and save it locally'), and implicitly separates itself from the gflow_upscale_video sibling by scoping to images. An agent can tell what this does without reading the schema.

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?

Makes the usage conditions concrete by gating scale on subscription tier (4k requires Ultra; Pro/Plus support 2k) and scoping to platform-generated Flow images, so the agent knows which invocations are valid. It never explicitly names an alternative tool (e.g. download_media or generate_image), so the when-not guidance is inferred rather than stated.

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