SatisfactoryMCP

Overview Schema Source Related Servers Discussions Admin

commission_plan

Read-onlyIdempotent

Determines the wave-by-wave energisation order for a built plant so each startup wave fits available grid headroom and generator output, preventing fuse trips.

Instructions

Startup order for a built plant: which blocks to energise in which wave without blowing the fuse.

Not a build order: build everything first, then energise wave by wave. A wave's consumer draw must fit in headroom plus the output of generators already burning, or the fuse blows and stops the whole grid until reset by hand. Generators energise free and pay for the next wave.

Input Schema

Name	Required	Description
`plan`	Yes	a saved plan's name or pin:N, or the solve: handle plan_factory printed
`save`	No
`as_of`	No	pin to one save: the sav:… token an earlier answer printed
`limit`	No
`world`	No
`offset`	No
`biomass`	No	count hand-fed biomass burners as generation; omitted: the shared setting
`headroom_mw`	No	grid power free for startup; default reads it from the save

Schema Changelog

Changes observed during successful MCP inspections.

Changed41 schema fields changedv0.3.0Oct 31, 2026

removedInput schema / properties / allow_sinks

Removed value: -{
-  "default": true,
-  "title": "Allow Sinks",
-  "type": "boolean"
-}

removedInput schema / properties / as_of / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / as_of / description

Previous value: -"pin to one world state: a sav:… token from an earlier answer"New value: +"pin to one save: the sav:… token an earlier answer printed"

removedInput schema / properties / as_of / title
```
Removed value: -"As Of"
```
addedInput schema / properties / as_of / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / biomass / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / biomass / title
```
Removed value: -"Biomass"
```
addedInput schema / properties / biomass / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedInput schema / properties / clocks

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "number"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Clocks"
-}

removedInput schema / properties / exclude_recipes

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Exclude Recipes"
-}

removedInput schema / properties / export_minimums

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {
-        "type": "number"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Export Minimums"
-}

removedInput schema / properties / exports

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Exports"
-}

removedInput schema / properties / extractor_clocks

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "number"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Extractor Clocks"
-}

removedInput schema / properties / headroom_mw / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / headroom_mw / title
```
Removed value: -"Headroom Mw"
```
addedInput schema / properties / headroom_mw / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedInput schema / properties / limit / description
```
Removed value: -"max rows (hard cap 25)"
```
removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

removedInput schema / properties / machine_cost_mw

Removed value: -{
-  "default": 5,
-  "title": "Machine Cost Mw",
-  "type": "number"
-}

removedInput schema / properties / objective

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "omitted: min_raw_power with export_minimums, else max_mw",
-  "title": "Objective"
-}

addedInput schema / properties / offset / minimum
```
Added value: +0
```
removedInput schema / properties / offset / title
```
Removed value: -"Offset"
```

removedInput schema / properties / only_free_nodes

Removed value: -{
-  "default": false,
-  "title": "Only Free Nodes",
-  "type": "boolean"
-}

removedInput schema / properties / only_recipes

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Only Recipes"
-}

removedInput schema / properties / plan / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / plan / default
```
Removed value: -null
```

changedInput schema / properties / plan / description

Previous value: -"recall a saved plan by name"New value: +"a saved plan's name or pin:N, or the solve: handle plan_factory printed"

removedInput schema / properties / plan / title
```
Removed value: -"Plan"
```
addedInput schema / properties / plan / type
```
Added value: +"string"
```

removedInput schema / properties / save / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / save / title
```
Removed value: -"Save"
```

addedInput schema / properties / save / type

Added value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / sloops

Removed value: -{
-  "default": 0,
-  "title": "Sloops",
-  "type": "integer"
-}

removedInput schema / properties / sources

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Sources"
-}

removedInput schema / properties / target_item

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Target Item"
-}

removedInput schema / properties / water_extractors

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Water Extractors"
-}

removedInput schema / properties / world / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / world / title
```
Removed value: -"World"
```
addedInput schema / properties / world / type
```
Added value: +[
+  "string",
+  "null"
+]
```
addedInput schema / required
```
Added value: +[
+  "plan"
+]
```

removedInput schema / title

Removed value: -"commission_planArguments"

Changed5 schema fields changedv0.2.0Oct 15, 2026

addedInput schema / properties / biomass

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "count hand-fed biomass burners as generation; omitted: the shared setting",
+  "title": "Biomass"
+}

addedInput schema / properties / objective / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / objective / default
```
Previous value: -"max_mw"New value: +null
```

addedInput schema / properties / objective / description

Added value: +"omitted: min_raw_power with export_minimums, else max_mw"

removedInput schema / properties / objective / type
```
Removed value: -"string"
```

Changed3 schema fields changedSep 27, 2026

addedInput schema / properties / as_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "pin to one world state: a sav:… token from an earlier answer",
+  "title": "As Of"
+}

changedInput schema / properties / limit / default
```
Previous value: -60New value: +25
```

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Goes well beyond the readOnlyHint/idempotentHint annotations by explaining the underlying mechanic: a wave must fit headroom plus running generator output, or 'the fuse blows and stops the whole grid until reset by hand.' That consequence framing is genuinely useful context even though the tool itself is a safe read. It stops short of saying what the tool returns or that computing costs nothing.

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 core statement in the first sentence, and every subsequent sentence adds domain meaning rather than filler. The hard line wrapping makes it slightly harder to scan than it needs to be, but there is no wasted content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the domain model (waves, headroom, fuse) well for a complex 8-parameter tool, and annotations already assure it is non-destructive. However, with no output schema and no statement of what the returned plan looks like or whether it is paginated (limit/offset), an agent still lacks a picture of the result.

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

Parameters3/5

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

Schema coverage is 50% and 8 parameters exist; the description names no parameters at all, so plan/save/as_of/limit/world/offset rely entirely on schema text (and several have none). It indirectly illuminates headroom_mw by explaining the headroom concept ('headroom plus the output of generators already burning'), which is real added meaning, but not enough to compensate for the undocumented half.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: 'Startup order for a built plant: which blocks to energise in which wave.' It explicitly distinguishes itself from a build order, which separates it from build-oriented siblings like site_plan and plan_factory, though it never names a sibling directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'Not a build order: build everything first, then energise wave by wave' clearly states the precondition and when this tool applies. It gives a strong usage condition but never names an alternative tool (e.g. plan_factory, site_plan) for the build-order case, leaving the routing implicit.

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

commission_plan

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools