SatisfactoryMCP

Overview Schema Source Related Servers Discussions Admin

factory_query

Read-onlyIdempotent

Inspect one factory from a Satisfactory save to see what it makes, needs, draws, or exchanges, with views for machines, recipes, balance, power, nodes, links, and issues.

Instructions

One question about one factory: what it makes, needs, draws or touches; show= takes several views.

Every rate is nameplate (at the saved clock) and measured (scaled by each machine's 300 s productivity window, so an idle line measures 0 without being broken); unmonitored machines are shown apart. offset pages every table at once.

Input Schema

Name	Required	Description	Default
`save`	No
`show`	No	comma-separated: summary (size, position, top recipes, net power) \| machines (building, recipe, clock) \| recipes \| buildings \| balance (per item produced, consumed, net) \| inputs (net deficit, fed from outside) \| outputs (net surplus) \| internal (made and eaten inside) \| power (draw vs generation) \| nodes (under its extractors) \| links (material exchanged with other factories) \| issues (paused, recipe-less, unresolved)	summary
`as_of`	No	pin to one save: the sav:… token an earlier answer printed
`limit`	No
`world`	No
`offset`	No
`factory`	Yes	a factory name or one selector term, e.g. proposal:3

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv0.3.0Oct 31, 2026

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"
+]
```

changedInput schema / properties / factory / description

Previous value: -"a label name, or any selector e.g. 'proposal:3'"New value: +"a factory name or one selector term, e.g. proposal:3"

removedInput schema / properties / factory / title
```
Removed value: -"Factory"
```
removedInput schema / properties / limit / description
```
Removed value: -"max rows (hard cap 25)"
```
removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

removedInput schema / properties / of

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "retired -- write show= instead",
-  "title": "Of"
-}

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

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"
+]

changedInput schema / properties / show / description

Previous value: -"comma-separated: summary, machines, recipes, buildings, balance, inputs, outputs, internal, power, nodes, links, issues"New value: +"comma-separated: summary (size, position, top recipes, net power) | machines (building, recipe, clock) | recipes | buildings | balance (per item produced, consumed, net) | inputs (net deficit, fed from outside) | outputs (net surplus) | internal (made and eaten inside) | power (draw vs generation) | nodes (under its extractors) | links (material exchanged with other factories) | issues (paused, recipe-less, unresolved)"

removedInput schema / properties / show / title
```
Removed value: -"Show"
```

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"
+]
```

removedInput schema / title

Removed value: -"factory_queryArguments"

Changed7 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"
+}

addedInput schema / properties / of / anyOf

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

changedInput schema / properties / of / default
```
Previous value: -"summary"New value: +null
```

changedInput schema / properties / of / description

Previous value: -"comma-separated: summary, machines, recipes, buildings, balance, inputs, outputs, power, nodes, links, issues"New value: +"retired -- write show= instead"

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

addedInput schema / properties / offset

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

addedInput schema / properties / show

Added value: +{
+  "default": "summary",
+  "description": "comma-separated: summary, machines, recipes, buildings, balance, inputs, outputs, internal, power, nodes, links, issues",
+  "title": "Show",
+  "type": "string"
+}

First observedv0.1.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes meaningfully beyond them: it explains nameplate vs. measured rates, the 300 s productivity window that makes an idle line read zero legitimately, that unmonitored machines are reported separately, and that offset paginates all tables jointly. That is exactly the kind of semantics an agent needs to interpret results. It stops short of covering error behavior (unknown/ambiguous factory, invalid view) or anything about the untokenized parameters.

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?

Three tight lines, front-loaded with purpose, with no filler sentences. The compression is aggressive to the point of near-crypticity ("what it makes, needs, draws or touches"), but every clause carries information.

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?

For a 7-parameter read tool with no output schema, the description adequately frames what the result means (rate semantics, unmonitored machines, cross-table paging). It leaves gaps on four of the seven parameters and on failure modes when the factory selector does not resolve, which matters given how many sibling tools could be confused with it.

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

Parameters2/5

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

Schema coverage is only 43%, so the description needs to compensate for undocumented parameters — and it largely does not. It adds real meaning for `offset` (pages every table at once) and reinforces `show`, but `save`, `limit`, `world`, and the exact selector semantics of `factory` go unaddressed in the description while also lacking schema descriptions.

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?

The opening states a concrete scope ("One question about one factory") and enumerates the questions it answers (makes, needs, draws, touches) plus the multi-view mechanism via `show=`. It is clear what the tool returns, but it does nothing to distinguish itself from siblings like factory_health, factory_floors, factory_map, or trace_upstream that also read a single factory.

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

Usage Guidelines3/5

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

Usage is only implicit: the agent is told `show=` takes several views and that views can be combined, which implies "prefer this over multiple calls." There is no when-to-use / when-not-to-use statement, no mention of how to find a factory name (e.g., list_factories) if `factory` is unknown, and no exclusion against sibling read tools.

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

factory_query

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools