Super Artifacts

Stage files for a publish

super_upload

Stage images, video or big files for a publish without sending their bytes in a call. Declare each file’s path and exact bytes; the result carries an uploadId and one url per file. PUT each file to its URL (curl -T, no credentials), then super_publish with uploads. Not index.html: that is html; small assets can ride inline as the publish’s files. Same limits as files; a staged set expires after 30 minutes, and at most 5 wait unpublished at once.

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": {
      "files": "<files>"
    },
    "name": "super_upload"
  }
}

Input Schema

Name	Required	Description	Default
`files`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover openWorldHint/destructiveHint, so the description carries the burden and delivers: staged sets expire after 30 minutes, at most 5 can wait unpublished, PUTs require no credentials, and sha256 is checked on upload. This is exactly the operational context the agent needs before committing.

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?

Dense but front-loaded: the staging concept and required declarations come first, followed by the PUT/publish workflow and limits. No sentence is redundant.

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?

With no output schema, the description still explains the return shape (uploadId plus per-file URLs) and the full call sequence. Nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is nominally 0%, but the description explains that each entry declares a `path` and an exact `bytes` value, and that the result carries an `uploadId` and one `url` per file. The nested sha256/contentType fields are documented in the schema itself, so the combination is nearly complete.

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 — stage images, video or big files for a publish — and immediately distinguishes this path from inline `files` and from `html`. An agent can identify the tool's role without opening 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 Guidelines5/5

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

Gives explicit routing: use this when bytes are too big to send in a call, use `html` for index.html, use inline `files` for small assets, and follow up with super_publish using `uploads`. When-to-use and when-not-to-use are both named.

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

All Super Artifacts tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?