Skip to main content
Glama
runapi-ai

Topaz MCP Server

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

upscale_image

Submit a Topaz AI upscaling task to raise image resolution by 1x, 2x, or 4x; returns a task id and output URLs, with optional polling until complete.

Instructions

Create a Topaz task on RunAPI (upscale image). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
timeout_msNo
callback_urlNoWebhook URL for terminal Task delivery. Declared type: string.
upscale_factorYesImage upscale multiplier. Declared type: integer. Known values: 1, 2, 4.
poll_interval_msNo
source_image_urlYesPublic source image URL. Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / callback_url / description
      Previous value: -"Webhook URL for terminal Task delivery."New value: +"Webhook URL for terminal Task delivery. Declared type: string."
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "topaz-upscale-image"
-]
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / source_image_url / description
      Previous value: -"Public source image URL."New value: +"Public source image URL. Declared type: string."
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / upscale_factor / description
      Previous value: -"Image upscale multiplier."New value: +"Image upscale multiplier. Declared type: integer. Known values: 1, 2, 4."
    • removedInput schema / properties / upscale_factor / enum
      Removed value: -[
-  1,
-  2,
-  4,
-  8
-]
    • changedInput schema / properties / upscale_factor / type
      Previous value: -"number"New value: +"integer"
  2. Changed5 schema fields changedv0.1.7
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "Webhook URL for terminal Task delivery.",
+  "type": "string"
+}
    • addedInput schema / properties / source_image_url / description
      Added value: +"Public source image URL."
    • addedInput schema / properties / source_image_url / type
      Added value: +"string"
    • addedInput schema / properties / upscale_factor / description
      Added value: +"Image upscale multiplier."
    • changedInput schema / required
      Previous value: -[
-  "upscale_factor"
-]New value: +[
+  "source_image_url",
+  "upscale_factor"
+]
  3. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation is asynchronous and returns a task id, status and output URLs, but says nothing about cost, auth requirements, failure behavior, or the polling semantics implied by wait/timeout_ms/poll_interval_ms.

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?

Two tight sentences with the action front-loaded and the return shape second. The parenthetical '(upscale image)' is mildly redundant with the tool name but costs almost nothing.

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 7-parameter, no-annotation, no-output-schema tool, the description does compensate by naming the return fields, but it omits how the async flow works (wait vs callback), cost implications, and any error behavior — all of which an agent needs to invoke this correctly.

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 71%, so the schema already documents most parameters (wait, model, callback_url, upscale_factor, source_image_url). The description adds no parameter-level meaning beyond that, so the baseline 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?

States a concrete action and resource: creating a Topaz task to upscale an image, with the async-task framing made explicit. It is distinguishable from upscale_video by resource, though it never names that sibling or contrasts itself with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus upscale_video, or when to let the default wait=true poll versus supplying a callback_url. The description also does not mention check_pricing or get_task, which are the obvious companions for a paid async job.

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

Deploy Server

Other Tools