blazie

name	blazie
description	Work against a blazie cluster through the control plane's MCP server — run Lua against worlds, claim worlds, read how a cluster is opening. Use when the task touches a blazie backend.

blazie

GENERATED by just mcp-skill from web/lib/control/mcp.ts. Do not edit — the tool array is the source, and just check fails when this file disagrees with it.

What you are talking to

The control plane, not a cluster. It holds every credential and performs the operations; you hold a grant and never a credential. That is deliberate: anything you read can instruct you, so your token is assumed compromised and bounded by a remit rather than trusted.

A remit says which worlds you may name, whether you may open or remove clusters, and how many may run at once (never more than 10). It expires — at most 90 days.

The rule that matters most

Every refusal carries a repair. A boundary here never rejects without saying how to comply, so when a tool answers with an error, the repair is the instruction — read it and follow it rather than retrying the same call or guessing.

Tools

clusters — The clusters you hold

List the clusters this grant's owner holds, with whether each is answering. A running blazie, reachable at an address, holding worlds. One or more nodes that agree on who owns which world — from outside, the thing you point a console or a client at; from inside, the set of nodes sharing name claims. Both are the same machines, so both are this word. You OPEN a cluster, the verb a world already uses.

Takes nothing.

worlds — The worlds a cluster holds

Which worlds this grant may name on a cluster. Where data lives, and what a chunk of Lua sees: an append-only sequence of facts, named and claimed by whoever holds it. A world is readable, forkable and deletable on its own; a tenant is one or more worlds. Nothing in one is ever rewritten, so a correction is a later fact and the earlier one still answers at the snapshot it was written into.

argument
cluster	required	string — The cluster's name.

run — Run Lua against a world

Run a chunk of Lua against one world and get back what it returned, plus the snapshot name it read. Writes land as facts. Where data lives, and what a chunk of Lua sees: an append-only sequence of facts, named and claimed by whoever holds it. A world is readable, forkable and deletable on its own; a tenant is one or more worlds. Nothing in one is ever rewritten, so a correction is a later fact and the earlier one still answers at the snapshot it was written into. Pass as: "job" only when the chunk must reach the network — a formula deliberately cannot, and that fence is why a formula's numbers can be trusted.

argument
cluster	required	string — The cluster's name.
world	required	string — The world to run against.
source	required	string — The Lua to run.
as	optional	formula · job — formula cannot reach the network. job can. Defaults to formula.

claim — Claim a world

Take a world name on a cluster and hold it. Names are first-come on a cluster, and one already held is refused rather than joined. Where data lives, and what a chunk of Lua sees: an append-only sequence of facts, named and claimed by whoever holds it. A world is readable, forkable and deletable on its own; a tenant is one or more worlds. Nothing in one is ever rewritten, so a correction is a later fact and the earlier one still answers at the snapshot it was written into.

argument
cluster	required	string — The cluster's name.
world	required	string — The name to take.

opening — How a cluster is getting on

What a machine said on its way to becoming a cluster, oldest first — booted, packages, docker, pulled, serving, tunnelled. The sequence up to a failure is most of the diagnosis, and a machine has no password and no key, so this is the only account of it there is.

argument
cluster	required	string — The cluster's name.

open_cluster — Open a cluster

Make a machine, install blazie on it, and put it behind a tunnel. This SPENDS MONEY and takes two or three minutes. A running blazie, reachable at an address, holding worlds. One or more nodes that agree on who owns which world — from outside, the thing you point a console or a client at; from inside, the set of nodes sharing name claims. Both are the same machines, so both are this word. You OPEN a cluster, the verb a world already uses. Bounded by the grant: it refuses past the ceiling on how many may run at once.

argument
name	required	string — What to call it. Becomes .blazie.dev.
zone	optional	string — Where. Defaults to the first available.
plan	optional	string — How big. Defaults to the smallest.

remove_cluster — Remove a cluster

Destroy a cluster's machine and every world on it. This CANNOT BE UNDONE. Refused unless the grant was given removal deliberately, which is separate from opening for that reason.

argument
cluster	required	string — The cluster's name.
sure	required	boolean — Must be true. There is no undo.