Skip to main content
Glama
Sign In

Supero

by io.github.supero-platform
OverviewDiscussions(2)Admin

build_go_live

Destructive

PERMANENT deploy: promote a published version to a PERMANENT public URL at .supero.live (managed Cloud Run) — unlike build_deploy(target='cloud_ephemeral'), which is a ~30-min throwaway. If version_uuid/file_id are omitted, the latest published version for the project is used. Returns public_url + poll_url; poll with build_deploy_status until live, then build_smoke_test the public_url. build_teardown removes it. Requires a domain- or project-admin API key + platform cloud-deploy enablement.

Input Schema

NameRequiredDescriptionDefault
file_idNoDefault: the resolved version's web artifact file_id.
project_uuidYesProject UUID (from build_list_projects or build_create_project).
version_uuidNoDefault: latest published version.
acknowledge_findingsNoExplicitly accept outstanding build_audit CRITICAL findings so go-live may proceed when the audit gate is enforced: [{fingerprint, reason}] (reason >= 15 characters; recorded with the version in the response). BLOCKER findings cannot be acknowledged — fix them. Fix findings instead whenever possible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / acknowledge_findings
      Added value: +{
+  "description": "Explicitly accept outstanding build_audit CRITICAL findings so go-live may proceed when the audit gate is enforced: [{fingerprint, reason}] (reason >= 15 characters; recorded with the version in the response). BLOCKER findings cannot be acknowledged — fix them. Fix findings instead whenever possible.",
+  "items": {
+    "properties": {
+      "fingerprint": {
+        "description": "The finding's fingerprint from build_audit.",
+        "type": "string"
+      },
+      "reason": {
+        "description": "Why it is acceptable to go live with it.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "fingerprint",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project_uuid / description
      Added value: +"Project UUID (from build_list_projects or build_create_project)."
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annos already flag destructiveHint=true and non-idempotent, and the description adds real context beyond them: required domain/project-admin key + platform cloud-deploy enablement, the permanence of the URL vs a temporary one, the return shape (public_url + poll_url), and that teardown is the removal mechanism.

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?

Front-loaded with the critical distinction (PERMANENT vs ephemeral), then defaults, then return/polling chain, then teardown, then prerequisites. Dense but every sentence carries distinct, actionable information — no filler.

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?

No output schema exists, but the description discloses the return fields (public_url, poll_url) and the exact follow-up calls to confirm liveness and smoke-test. For a destructive 4-param deploy tool this is complete enough to invoke correctly on the first try.

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 100%, so the baseline is 3; the description still adds value by explaining that omitting version_uuid/file_id resolves to the latest published version and by framing acknowledge_findings around the audit gate (BLOCKER findings cannot be accepted). That extra gate semantics goes beyond the schema text.

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 the specific verb (promote/deploy) and resource (published version → permanent public URL at <service>.supero.live) and draws the contrast with build_deploy(target='cloud_ephemeral') explicitly. An agent can distinguish this from every sibling deploy tool without opening a 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?

Explicit when-to-use vs the ephemeral sibling (~30-min throwaway), states the default resolution behavior when version_uuid/file_id are omitted, and gives the required follow-up chain (build_deploy_status → build_smoke_test). Also names build_teardown as the removal path.

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

All Supero toolsInspect
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