StockCake

Upscale Image

upscale_image

Upscale a StockCake image or one of your edited images 2x, 4x or 8x (lossless PNG output). Plan quality caps apply; charges credits otherwise. Waits up to 45 s, then returns a job_id for get_job. Requires a free StockCake account (the host will prompt to sign in).

Input Schema

TableJSON Schema

Name	Required	Description
`image`	Yes	A StockCake image id (from search_images), one of your own edited image ids (from a previous result), or a job_id. Never a URL.
`scale`	Yes
`context`	Yes	In one sentence, what is the user trying to make or find?
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "credits_charged": {
-        "type": "number"
-      },
-      "image": {
-        "additionalProperties": false,
-        "properties": {
-          "id": {
-            "description": "Edited image id — pass it to download_image or as an image reference",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "url": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "url"
-        ],
-        "type": "object"
-      },
-      "job_id": {
-        "type": "string"
-      },
-      "status": {
-        "const": "completed",
-        "type": "string"
-      }
-    },
-    "required": [
-      "job_id",
-      "status",
-      "image",
-      "credits_charged"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "credits_charged": {
-        "type": "number"
-      },
-      "job_id": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "status": {
-        "const": "pending",
-        "type": "string"
-      }
-    },
-    "required": [
-      "job_id",
-      "status",
-      "credits_charged",
-      "message"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "code",
-      "message"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "credits_charged": {
+        "type": "number"
+      },
+      "image": {
+        "additionalProperties": false,
+        "properties": {
+          "dimensions": {
+            "anyOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "height": {
+                    "type": "number"
+                  },
+                  "width": {
+                    "type": "number"
+                  }
+                },
+                "required": [
+                  "width",
+                  "height"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Output pixel size; null when the file could not be probed"
+          },
+          "id": {
+            "description": "Edited image id — pass it to get_image (preview), download_image, or as an image reference",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "url",
+          "dimensions"
+        ],
+        "type": "object"
+      },
+      "job_id": {
+        "type": "string"
+      },
+      "status": {
+        "const": "completed",
+        "type": "string"
+      }
+    },
+    "required": [
+      "job_id",
+      "status",
+      "image",
+      "credits_charged"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "credits_charged": {
+        "type": "number"
+      },
+      "job_id": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "status": {
+        "const": "pending",
+        "type": "string"
+      }
+    },
+    "required": [
+      "job_id",
+      "status",
+      "credits_charged",
+      "message"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "code",
+      "message"
+    ],
+    "type": "object"
+  }
+]

First observedSep 28, 2026

TDQS

A4/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, idempotent=false): it discloses lossless PNG output, plan quality caps and credit charges, a 45 s wait before falling back to an async job_id handled by get_job, and a required free StockCake account with a host sign-in prompt. That is exactly the operational context an agent needs before committing to a non-idempotent, possibly billed call.

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?

Three tightly packed sentences, front-loaded with the action and scale options, then cost/cap behavior, then async and auth requirements. No filler and nothing repeated from the schema.

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 non-idempotent, credit-consuming, potentially asynchronous tool it covers billing, timing, continuation via get_job and the auth prerequisite, and an output schema exists so return values need no explanation. The only gap is the absence of any routing hint versus resize_image for the agent deciding between them.

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 coverage is 80%, so the schema already documents image sources, the scale consts, context, llm_model and conversation_id in detail. The description reinforces accepted image sources and the 2x/4x/8x scale values but adds no syntax or semantics the schema lacks, 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 specific verb (upscale) and resource (StockCake or edited image), plus the exact multipliers 2x/4x/8x and lossless PNG output. It does not differentiate from the sibling resize_image, which also transforms image dimensions, so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it tells you the tool upscales existing images and that plan caps/billing apply, but never says when to choose it over resize_image or generate_image, nor what happens if the plan cap blocks the request beyond 'charges credits otherwise'.

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

All StockCake tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?