Flux Cloud

Restart, redeploy or remove app instances

flux_control_app

Destructive

restart: restarts containers. redeploy: pulls the image again and recreates containers (hard=true also wipes data). remove: uninstalls from nodes; the registration stays and the network re-spawns it elsewhere, so use flux_cancel_app to stop paying. Scope is one node (nodeIp) or every node running the app (global). Requires the owner key.

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": {
      "name": "<name>",
      "action": "<action>"
    },
    "name": "flux_control_app"
  }
}

Input Schema

Name	Required	Description	Default
`hard`	No	For redeploy: also delete the app data.
`name`	Yes
`scope`	No		global
`action`	Yes
`nodeIp`	No	Required for scope=node; also the node the global command is sent through.
`fluxIdPrivateKey`	No	WIF private key of the Flux ID that owns the app. Use a dedicated key from flux_generate_keys, never a main wallet key.
`paymentPrivateKey`	No	WIF private key of the Flux address that pays. Fund it with only what you intend to spend.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, and the description adds real context on top: hard=true wipes app data, remove is non-terminal because the registration persists and the app re-spawns elsewhere, and the owner key is required. This is exactly the behavioral detail an agent needs for a destructive multi-action tool.

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 every clause carries distinct decision-relevant information, front-loaded by action name so the agent can stop reading once it finds its action. No filler or restatement of the title.

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 destructive, key-requiring multi-action tool with no output schema, the description covers actions, scope, data-loss conditions and key needs. The only shortfall is that it doesn't indicate what the call returns or how long a redeploy/remove takes to settle, which would help an agent decide whether to poll.

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?

With schema coverage at 57%, the description compensates well by explaining the semantics of action (three values), hard (wipes data), scope (node vs global) and nodeIp's dual role. It does not mention paymentPrivateKey or clarify the owner-key parameter's exact mapping, leaving a small gap against the remaining undocumented schema entries.

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 the concrete resource (app containers/instances) and enumerates each verb with its distinct effect: restart restarts containers, redeploy re-pulls and recreates, remove uninstalls from nodes. It even distinguishes itself from the sibling flux_cancel_app, so an agent can route correctly without opening the 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?

Explicit when-to-use guidance per action, plus a clear when-not/alternative: remove leaves the registration so the network re-spawns it, therefore use flux_cancel_app to actually stop paying. Scope selection (node vs global) is also spelled out, which is the key decision an agent must make.

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

All Flux Cloud 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.