Skip to main content
Glama
lukszi

SatisfactoryMCP

by lukszi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unlocked_recipes

Retrieve recipes unlocked in a Satisfactory world, defaulting to alternate recipes and supporting pagination to list all available options.

Instructions

Which recipes this world has. Defaults to alternates, never all 872.

Sorted by name and paged with offset=, so the whole list is reachable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNo
as_ofNopin to one world state: a sav:… token from an earlier answer
limitNomax rows (hard cap 25)
worldNo
offsetNo
only_alternatesNo

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"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

B3.3/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 and does disclose real behavior: the default only_alternates filter, name sorting, and offset-based paging that makes the full list reachable. It does not disclose auth/permission needs, whether results are cached or expensive, or any return shape, leaving meaningful gaps for a no-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the scope/default constraint is front-loaded before the paging note. 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 6-parameter query tool with no output schema and no annotations, the description covers the essential quirks (default filter, sorting, pagination) but omits the meaning of save, world, as_of, and limit, so an agent can call it correctly only for the default case.

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 33%, so the description must compensate, and it does partially: it clarifies the only_alternates default and how offset= pages through results. It leaves save, world, as_of, and limit undocumented beyond the terse schema hints, so it falls short of full compensation without being empty.

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 resource and scope: 'Which recipes this world has', and quantifies the default ('defaults to alternates, never all 872'). An agent can tell this is a recipe-listing tool, though it never names or contrasts with siblings like search_recipes, recipe_detail, or alternates_for_item.

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

Usage Guidelines2/5

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

The description implies usage through the default-filter note but gives no explicit when-to-use or when-not-to-use guidance and no alternative routing against the ~50 sibling tools. An agent must infer whether this or search_recipes is the right call.

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