Super Artifacts

Change what an artifact serves, and to whom

super_artifact_set

DestructiveIdempotent

Change one artifact. version serves an existing version (a pointer move; nothing rebuilt or deleted). live turns its live room on or off; off disconnects every visitor, and Free has one room at a time. triggersEnabled is the owner’s kill switch for declared triggers (default on). notifyOnSubmission emails you for each new data submission (default off; edits send nothing; no answers in the mail). phase sets the live room’s phase. visibility widens or narrows who can open it; narrowing voids every viewer grant already issued, so each viewer is checked again. collection sets its gallery grouping label. delete removes the artifact with every version, share link and response, permanently; it needs confirm: true and goes alone. Fields apply in that order, and a refusal part-way names the ones already applied. Publishing a new version is super_publish.

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": {
      "artifact": "<artifact>"
    },
    "name": "super_artifact_set"
  }
}

Input Schema

Name	Required	Description
`live`	No
`phase`	No	The name a stream’s `revealAt` waits for; from then on that stream reads as public.
`delete`	No
`confirm`	No	Must be true to delete.
`version`	No
`artifact`	Yes	Artifact id or slug.
`collection`	No	Gallery grouping label, ≤ 60 chars. Empty clears it.
`visibility`	No	private: Restricted (default). organization: anyone at the workspace. public: anyone with the link.
`triggersEnabled`	No
`notifyOnSubmission`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- addedInput schema / properties / triggersEnabled
```
Added value: +{
+  "type": "boolean"
+}
```
Changed1 schema field changedOct 28, 2026
- addedInput schema / properties / notifyOnSubmission
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / phase / description

Added value: +"The name a stream’s `revealAt` waits for; from then on that stream reads as public."

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 declare destructiveHint=true and idempotentHint=true, and the description earns credit beyond them by disclosing consequences: turning `live` off disconnects every visitor, the Free plan allows one room, narrowing `visibility` voids every issued viewer grant, and `delete` removes every version, share link and response permanently. It also explains the partial-failure contract (`applied`), which no annotation conveys.

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?

Front-loaded with the tool's purpose and alternative, then one clause per field, so every sentence carries information. The single dense paragraph of semicolon-chained clauses is harder to scan than a short list, which is the only structural weakness.

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?

For a 10-parameter mutation tool with a destructive delete path and no output schema, the description covers ordering, defaults, irreversible effects, plan limits, and how failures report partial application. Nothing an agent needs to call it safely appears to be missing.

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 only 50%, but the description compensates for nearly every gap: it supplies defaults the schema omits (`triggersEnabled` default on, `notifyOnSubmission` default off), clarifies that edits send no mail and mails contain no answers, and explains `phase`, `collection` and `visibility` consequences. Only the `artifact` identifier is left to the schema.

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?

The description names a specific verb and resource ('Change one artifact') and then enumerates every mutable facet: version pointer, live room, triggers, submission notifications, phase, visibility, collection, deletion. It explicitly separates itself from super_publish ('Publishing a new version is super_publish'), so an agent can pick between the two without opening schemas.

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?

Each field carries its own when-to-use semantics: `version` is a pointer move rather than a rebuild, `delete` requires `confirm: true` and 'goes alone', and publishing is redirected to super_publish. It even specifies application order and that a mid-way refusal reports which fields were already applied.

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?