Skip to main content
Glama
lukszi

SatisfactoryMCP

by lukszi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_context

Idempotent

Fetch the open page's view, plan/version, tab, selection, save sync, queued asks, advisories, and recent plan/chat updates before handling 'this', 'here', or ask/pin IDs.

Instructions

What the web page has open; call first when the user says 'this', 'here' or quotes an ask: or pin: id.

Names the page's view, plan and version, tab and selection, whether the page reads the same save as you, queued asks, advisories (adv: ids), and every plan version or chat solve by someone else since your last look. Listed asks are marked seen on the page; pass answered= once answered. dismissed= hides an advisory, only when the user asks.

Input Schema

NameRequiredDescriptionDefault
saveNo
worldNo
answeredNoask:N ids you answered; "ask:7 <answer>" adds a line
dismissedNoadv: ids to hide on the page; "adv:3f9a snooze" hides for 1 h of play

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv0.3.0
    • removedInput schema / properties / answered / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / answered / description
      Previous value: -"ask:N ids you have answered, each may add a line: \"ask:7 <answer>\""New value: +"ask:N ids you answered; \"ask:7 <answer>\" adds a line"
    • addedInput schema / properties / answered / items
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / answered / title
      Removed value: -"Answered"
    • addedInput schema / properties / answered / type
      Added value: +[
+  "array",
+  "null"
+]
    • removedInput schema / properties / dismissed / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / dismissed / items
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / dismissed / title
      Removed value: -"Dismissed"
    • addedInput schema / properties / dismissed / type
      Added value: +[
+  "array",
+  "null"
+]
    • 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 / 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: -"ui_contextArguments"
  2. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / answered
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ask:N ids you have answered, each may add a line: \"ask:7 <answer>\"",
+  "title": "Answered"
+}
    • addedInput schema / properties / dismissed
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "adv: ids to hide on the page; \"adv:3f9a snooze\" hides for 1 h of play",
+  "title": "Dismissed"
+}
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses important side effects beyond the annotations: listed asks are marked seen on the page, answered= records an answer, and dismissed= hides an advisory only when the user asks. This is consistent with readOnlyHint=false and useful for an agent to know before invoking the tool, though it does not discuss permissions or response format.

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 description is dense but front-loaded with the critical 'call first' condition and then packs the returned context and side-effect guidance into a compact paragraph. It is appropriately sized for a complex context tool, though the run-on enumeration could be easier to scan.

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 does the necessary work of enumerating what the tool returns: view, plan/version, tab/selection, save consistency, queued asks, advisories, and recent external changes. It also covers triggers and side effects, leaving only the save/world parameters insufficiently explained.

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 50%, and the description adds useful meaning for answered= and dismissed= beyond the schema descriptions. However, the save and world parameters are undocumented in both schema and description, so the description only partially compensates for the coverage gap.

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 identifies this as a page-context retrieval tool: it states 'What the web page has open' and enumerates the page view, plan/version, tab/selection, queued asks, advisories, and recent changes. The purpose is specific, though it does not explicitly differentiate itself from the many sibling tools.

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?

It gives a strong trigger condition: 'call first when the user says "this", "here" or quotes an ask: or pin: id.' It also constrains side-effecting parameters with 'pass answered= once answered' and 'dismissed= hides an advisory, only when the user asks.' It does not name alternatives or when-not-to-use cases.

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