Skip to main content
Glama
lukszi

SatisfactoryMCP

by lukszi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

select_machines

Preview which machines a selector picks before naming them; filter by product, recipe, building, location, or label to isolate the intended factory setup.

Instructions

Preview which machines a selector picks, before naming them.

Worth running first on anything product-based: 17 machines make Concrete on the reference save, but 15 of them are a construction feed inside the steel site and only one is the player's "concrete setup".

slab:<n> answers "what stands on this platform", and answers it for an empty one too: a poured platform with nothing on it yet is described rather than refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNo
as_ofNopin to one world state: a sav:… token from an earlier answer
splitNokeep only the largest spatial cluster
worldNo
expandNopull in everything belted to the result
selectYesselector terms, ANDed. product:<item> | recipe:<name> | building:<class or name> | near:<place>@<radius_m> | base:<n> | line:<n> | slab:<n> | proposal:<n> | label:<name> | machine:<instance> | all. Terms are ANDed; comma-separated values inside one term are ORed; prefix a term with '-' to exclude it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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"
+}
    • changedInput schema / properties / select / description
      Previous value: -"selector terms, ANDed. product:<item> | recipe:<name> | building:<class or name> | near:<x,y@radius_m or label@radius_m> | base:<n> | line:<n> | slab:<n> | proposal:<n> | label:<name> | all. Terms are ANDed; comma-separated values inside one term are ORed; prefix a term with '-' to exclude it"New value: +"selector terms, ANDed. product:<item> | recipe:<name> | building:<class or name> | near:<place>@<radius_m> | base:<n> | line:<n> | slab:<n> | proposal:<n> | label:<name> | machine:<instance> | all. Terms are ANDed; comma-separated values inside one term are ORed; prefix a term with '-' to exclude it"
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses two behaviors beyond expectation: product selectors over-match (construction feed inside the steel site) and `slab:<n>` describes an empty platform rather than refusing. However it never states the tool is read-only/preview-only in safety terms, nor how results are returned, leaving gaps for a 6-param tool with zero annotation coverage.

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 purpose, then one grounded example and one edge-case note. Every sentence carries information; the Concrete example is a bit long but earns its place by teaching the over-match trap.

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?

No output schema and no annotations, so the description must carry the load. It covers purpose, the key selector gotcha, and slab behavior adequately for a preview tool, though it omits read-only framing and the meaning of save/world/as_of parameters, which an agent would still need.

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 67%, and the description meaningfully supplements it: it explains the semantics of product-based selectors (over-matching and how they resolve) and the special `slab:<n>` term including its empty-platform behavior. It does not address save/world/as_of/split/expand, but it adds real semantic value beyond the schema's terse term list.

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?

States a specific verb and resource ('Preview which machines a selector picks') and adds the dry-run framing 'before naming them,' which signals it is the read-only preview preceding naming tools. It's clear, though it doesn't name the specific sibling (e.g. name_factory) it pairs with.

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?

'Worth running first on anything product-based' gives an explicit when-to-use condition and the concrete example (Concrete pulling 17 machines with only one intended) tells the agent exactly when this tool adds value. No explicit when-not or named alternative, so not a 5.

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