Skip to main content
Glama
lukszi

SatisfactoryMCP

by lukszi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rank_build_sites

Read-onlyIdempotent

Ranks candidate extraction sites for one resource, best first, by scoring reachable untapped capacity against spread, distance, purity, and terrain to guide placement.

Instructions

Rank fields for a new extraction site of one resource, best first.

Scores untapped reachable capacity against spread, distance to your buildings, purity and terrain; every raw component is shown to re-weight, the score is a start, not a verdict. sources= narrows the area with search_resource_nodes' selectors; omit for the whole map. No offset: raise limit or narrow sources.

Input Schema

NameRequiredDescriptionDefault
saveNo
as_ofNopin to one save: the sav:… token an earlier answer printed
limitNo
worldNo
sourcesNo
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv0.3.0
    • 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 / limit / description
      Removed value: -"max rows (hard cap 25)"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / resource / title
      Removed value: -"Resource"
    • 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 / sources / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / sources / items
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / sources / title
      Removed value: -"Sources"
    • addedInput schema / properties / sources / type
      Added value: +[
+  "array",
+  "null"
+]
    • removedInput schema / properties / top
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "deprecated alias for limit",
-  "title": "Top"
-}
    • 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: -"rank_build_sitesArguments"
  2. Changed6 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 / limit
      Added value: +{
+  "default": 5,
+  "description": "max rows (hard cap 25)",
+  "maximum": 25,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / top / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / top / default
      Previous value: -5New value: +null
    • addedInput schema / properties / top / description
      Added value: +"deprecated alias for limit"
    • removedInput schema / properties / top / type
      Removed value: -"integer"
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral detail: every raw scoring component is exposed for re-weighting, the score is advisory, and there is no offset so pagination must go through limit/sources. That is useful beyond-annotation context, though permissions/cost/return shape aren't discussed.

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 purpose and ranking explanation are front-loaded and dense with signal; the trailing notes on sources and pagination earn their place. Slightly verbose in the middle clause about raw components but no true waste.

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 read-only tool with no output schema, the description adequately covers ranking semantics, the sources selector, and pagination, but does not explain the save/as_of/world interplay that matters for result scoping. An agent could still mis-scope a call by guessing at those params.

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 17%, so the description must compensate. It usefully explains `sources` semantics and the `limit`-instead-of-offset rule, but leaves `resource` (the only required param), `world`, `save`, and `as_of` — including the distinction between save and as_of — entirely to the schema.

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?

States a specific verb and resource — 'Rank fields for a new extraction site of one resource, best first' — and immediately conveys the output ordering. An agent can distinguish it from search_resource_nodes, which it explicitly references as a complementary selector source.

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?

Gives a concrete use condition for `sources` (narrows the area, omit for whole map) and names the sibling whose selectors it accepts. It also explains the no-offset pagination rule. What's missing is a when-not-to-use-this / alternative-tool clause beyond the sources hint.

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