Skip to main content
Glama
lukszi

SatisfactoryMCP

by lukszi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

settings

Idempotent

Reads or changes shared factory-planning defaults—stage headroom, biomass, payback hours, and overclock behavior—only when you ask.

Instructions

Settings the page and chat share; change one only when the user asks.

stage_headroom: what diff_vs_save and commission_plan stage a plan against when it stores none. biomass: default of every biomass= parameter. payback_hours, overclock_last: what a plan that sets neither follows. The page's Settings tab shares the file and follows a change. Base map types are listed read-only.

Input Schema

NameRequiredDescriptionDefault
changeNosettings to change, e.g. {"stage_headroom": "nameplate"}; null resets one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • addedInput schema / properties / change / additionalProperties
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • removedInput schema / properties / change / anyOf
      Removed value: -[
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "boolean"
-        },
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / change / description
      Previous value: -"settings to change, e.g. {\"stage_headroom\": \"nameplate\"}; null resets"New value: +"settings to change, e.g. {\"stage_headroom\": \"nameplate\"}; null resets one"
    • removedInput schema / properties / change / title
      Removed value: -"Change"
    • addedInput schema / properties / change / type
      Added value: +[
+  "object",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"settingsArguments"
  2. Addedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive, idempotent, closed-world mutation. The description adds useful behavioral context beyond that: the settings file is shared with the page's Settings tab, changes are followed there, and base map types are listed read-only.

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?

The core constraint is front-loaded in the first sentence, and the following notes are compact and relevant. The wording is somewhat cryptic and line-broken, but it does not waste many words.

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 one-parameter settings tool with annotations and no output schema, the description is mostly adequate. It still leaves ambiguity around how current settings are read and what calling without a change returns, which matters because no output schema exists to clarify the response.

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, but the description adds real meaning for specific keys such as stage_headroom, biomass, payback_hours, and overclock_last. The schema handles the shape of 'change' and its null-reset behavior, while the description explains what several values control.

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

Purpose3/5

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

The description identifies the resource as shared settings and implies mutation via 'change one only when the user asks,' but it never states a clear verb such as get or update. It explains several setting keys, yet an agent still has to infer the core read/write behavior from the schema and annotations.

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?

The phrase 'change one only when the user asks' gives a real usage constraint, which is more than none. However, it does not say when to read versus write settings, nor does it name an alternative tool such as ui_context or any sibling for related configuration.

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

Deploy Server

Other Tools