Skip to main content
Glama
lukszi

SatisfactoryMCP

by lukszi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

explain_byproducts

Read-onlyIdempotent

Identify the byproduct that makes a factory plan infeasible and show sink or recipe consumers that can use it, including locked versus unlocked options.

Instructions

Which byproduct stalls a plan (INFEASIBLE) and what can consume it: sink (solids only) or recipes, unlocked vs locked.

Item balances are equalities, so an unconsumed byproduct makes the solve infeasible; a fluid must be consumed or packaged first. Reads an infeasible solve: handle too.

Input Schema

NameRequiredDescriptionDefault
itemNoone byproduct to focus on; omit = the whole plan
planYesa saved plan's name or pin:N, or the solve: handle plan_factory printed
saveNo
as_ofNopin to one save: the sav:… token an earlier answer printed
limitNo
worldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changedv0.3.0
    • 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 / 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 / item / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / item / description
      Added value: +"one byproduct to focus on; omit = the whole plan"
    • removedInput schema / properties / item / title
      Removed value: -"Item"
    • addedInput schema / properties / item / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / limit / description
      Removed value: -"max rows (hard cap 25)"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • 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"
-}
    • removedInput schema / properties / only_free_nodes
      Removed value: -{
-  "default": false,
-  "title": "Only Free Nodes",
-  "type": "boolean"
-}
    • addedInput schema / properties / plan
      Added value: +{
+  "description": "a saved plan's name or pin:N, or the solve: handle plan_factory printed",
+  "type": "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 / 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 / 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: -"explain_byproductsArguments"
  2. Changed5 schema fields changedv0.2.0
    • 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"
    • addedInput schema / properties / only_free_nodes
      Added value: +{
+  "default": false,
+  "title": "Only Free Nodes",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • 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"
+}
  4. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare it as a safe, read-only, idempotent operation. The description adds valuable domain behavior: item balances are equalities, unconsumed byproducts cause infeasibility, and fluids must be consumed or packaged first. Return format and pagination behavior are not described, but the domain context is strong.

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 purpose is front-loaded and the domain rationale is compact. The phrase 'handle too' is slightly cryptic, but overall the description is efficient and avoids unnecessary length.

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 6-parameter diagnostic tool with no output schema, the description explains the core return concept well: which byproduct stalls the plan and what can consume it. However, it leaves several parameters and full output details unspecified, so it is adequate but incomplete.

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 description coverage is only 50%, and the description does not explain the undocumented parameters such as save, limit, or world. It reinforces the concept of focusing on a byproduct or the whole plan, but does not fully compensate for the missing 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 description clearly states the tool identifies which byproduct makes a plan infeasible and what can consume it, including sinks and recipes. It is specific enough to separate this diagnostic tool from plan-building siblings, though it does not explicitly name alternatives.

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 'Reads an infeasible solve: handle too' gives implied context for when to use it, but there is no explicit when-not guidance or named alternative tool. Usage is inferable but not fully specified.

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