Skip to main content
Glama
lukszi

SatisfactoryMCP

by lukszi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

phase_requirements

Show how many items the Space Elevator still needs for each phase by reading live save data, while flagging the frozen deprecated per-phase table as untrusted.

Instructions

What the Space Elevator still wants, live record and deprecated record apart.

The per-phase item table in the save is DEPRECATED and frozen, so it is shown labelled rather than believed. Read the header line first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNo
as_ofNopin to one world state: a sav:… token from an earlier answer
worldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.1.0

TDQS

C2.7/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 it does disclose a genuine behavioral caveat: the per-phase item table is DEPRECATED and frozen, and is shown labelled rather than trusted. That is useful data-fidelity context. It still omits permissions, return shape, and error behavior.

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?

It is short and front-loads the subject before the deprecation caveat. The awkward line breaks and lore-flavored phrasing cost it a point, but there is little filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and three loosely documented parameters, the description should work harder. It leaves the return format, the meaning of save/world, and the tool's relationship to sibling phase/milestone tools to inference.

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 coverage is only 33% (only as_of is documented), and the description explains neither 'save' nor 'world', so it fails to compensate for the coverage gap. It does loosely gesture at the as_of concept ('pin to one world state') but that meaning already lives in the schema, adding nothing.

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 does identify a specific resource (Space Elevator phase requirements) and distinguishes live vs. deprecated records, which no sibling covers. However the verb is oblique ('what the Space Elevator still wants') and it never states cleanly that it returns per-phase item requirements. An agent can guess the domain but not the exact output.

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?

There is no when-to-use or when-not-to-use guidance, and no sibling alternative is named despite many plausible overlaps (milestones, mam_research, unlocked_recipes). The only procedural hint is 'Read the header line first,' which concerns reading the output, not deciding to call the tool.

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