SatisfactoryMCP

Overview Schema Source Related Servers Discussions Admin

collected_from_world

Read-onlyIdempotent

Track Satisfactory collectibles by counting existing, collected, and remaining slugs, sloops, spheres, mushrooms, and drop pods, then list coordinates or nearest leftovers.

Instructions

Map collectibles (slugs, sloops, spheres, mushrooms, drop pods): how many exist, taken, left, closest.

Existence is read from the installed game's map data, removal from the save's destroyed-actor list; remaining is the difference. show=census counts per category; collected and remaining list placements with coordinates; nearest lists remaining by distance from near=. A placement this save never loaded counts as remaining, flagged never_streamed.

Input Schema

Name	Required	Description	Default
`near`	No	'x,y' (m), 'me' or a factory; @<radius_m> keeps what is within; nearest defaults to you
`save`	No
`show`	No	census \| collected \| remaining \| nearest	census
`as_of`	No	pin to one save: the sav:… token an earlier answer printed
`group`	No	one category, e.g. 'power_slug_blue'; omit for all
`limit`	No
`world`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

removedInput schema / properties / group / anyOf

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

changedInput schema / properties / group / description

Previous value: -"one category, e.g. 'power_slug_blue'. Omit to see them all"New value: +"one category, e.g. 'power_slug_blue'; omit for all"

removedInput schema / properties / group / title
```
Removed value: -"Group"
```
addedInput schema / properties / group / 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 / mode

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

removedInput schema / properties / near / anyOf

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

changedInput schema / properties / near / description

Previous value: -"origin for show=nearest: 'x,y' in metres, 'me', or a factory name. Defaults to where the player is standing"New value: +"'x,y' (m), 'me' or a factory; @<radius_m> keeps what is within; nearest defaults to you"

removedInput schema / properties / near / title
```
Removed value: -"Near"
```

addedInput schema / properties / near / type

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

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

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: -"collected_from_worldArguments"

Changed8 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 / mode / anyOf

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

changedInput schema / properties / mode / default
```
Previous value: -"census"New value: +null
```

changedInput schema / properties / mode / description

Previous value: -"census | collected | remaining | nearest"New value: +"retired -- write show= instead"

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

changedInput schema / properties / near / description

Previous value: -"origin for mode=nearest: 'x,y' in metres, 'me', or a factory name. Defaults to where the player is standing"New value: +"origin for show=nearest: 'x,y' in metres, 'me', or a factory name. Defaults to where the player is standing"

addedInput schema / properties / offset

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

addedInput schema / properties / show

Added value: +{
+  "default": "census",
+  "description": "census | collected | remaining | nearest",
+  "title": "Show",
+  "type": "string"
+}

First observedv0.1.0Aug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent profile, and the description adds genuinely new behavioral context: existence comes from installed map data, removal from the save's destroyed-actor list, remaining is the difference, and never-loaded placements are counted as remaining and flagged never_streamed. It omits pagination behavior (limit capped at 25, offset) and the meaning of save/as_of/world for staleness.

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 resource and the counts before the mechanism, then mode descriptions. Dense and mostly waste-free, though the trailing provenance sentence is slightly buried and a stray blank line breaks the flow.

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?

With no output schema, the description usefully sketches what each show mode returns (per-category counts, coordinate listings, distance ordering). For an 8-parameter tool with 50% schema coverage, the unaddressed save/world/as_of/pagination semantics are the remaining gap.

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 only 50%, so the description must carry weight. It explains show modes, the near= syntax and the group category concept, but save, as_of, world, limit, and offset receive no explanation anywhere in the description, leaving several parameters semantically thin.

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

Purpose5/5

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

Opens with a concrete verb and resource — 'Map collectibles (slugs, sloops, spheres, mushrooms, drop pods)' — and immediately states the four quantities returned (exist, taken, left, closest). None of the siblings (show_on_map, world_summary, search_resource_nodes) touch save-state collectible accounting, so the tool is unmistakable.

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?

The show= enumeration (census | collected | remaining | nearest) is described functionally, so an agent can pick a mode from intent. It stops short of explicit 'when not to use this' or naming an alternative sibling for related map questions.

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

collected_from_world

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools