Skip to main content
Glama

factory_query

Ask about a factory in Satisfactory to see its production balance, power draw, inputs, outputs, machines, and links to other factories. Choose what to inspect: summary, balance, power, nodes, or issues.

Instructions

Ask one thing about one factory: what it makes, needs, draws, or touches.

of accepts several at once, e.g. "balance,power,links".

  • summary size, position, top recipes, net power

  • balance per-item produced vs consumed vs net -- the sign is the point

  • outputs net surplus: it leaves the factory, or it backs up

  • inputs net deficit: it has to be fed in from outside

  • machines every machine with its building, recipe and clock

  • recipes / buildings counts

  • power draw vs generation at saved clocks

  • nodes resource nodes its extractors sit on

  • links which other factories it exchanges material with

  • issues paused, recipe-less, or unresolved machines

Rates are NAMEPLATE at each machine's saved clock, not measured throughput. A starved factory still reports its full rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ofNocomma-separated: summary, machines, recipes, buildings, balance, inputs, outputs, power, nodes, links, issuessummary
saveNo
limitNomax rows (hard cap 25)
worldNo
factoryYesa label name, or any selector e.g. 'proposal:3'
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the critical fact that rates are nameplate at saved clocks, not measured throughput, and a starved factory still reports full rate. It also clarifies the semantics of 'balance', 'inputs', and 'outputs' (sign/direction). It doesn't mention pagination or error behavior, but the disclosed nuance is valuable.

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?

The description is front-loaded with the core purpose, uses compact bullet points for each 'of' option, and includes a necessary caveat about rates. Every sentence earns its place; no redundant fluff.

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?

For a complex multi-faceted query tool with no output schema, the description explains the scope of results for each 'of' value (e.g., summary: size, position, top recipes, net power) and adds the rate caveat. It doesn't discuss the output format itself, but given the breadth, it is reasonably complete. Save and world parameters are not explained, but they appear to be context selectors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds substantial meaning to the 'of' parameter by explaining each option's scope (e.g., 'outputs: net surplus: it leaves the factory, or it backs up'). Schema coverage is 60%, but the description compensates by enriching the key parameter beyond the schema's simple list. It also clarifies 'factory' as a label or selector, which is already in 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?

The description opens with a clear verb and resource: 'Ask one thing about one factory: what it makes, needs, draws, or touches.' It enumerates specific query categories (summary, balance, outputs, etc.) which both clarifies purpose and distinguishes it from sibling tools like factory_map or factory_health.

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 first line implies usage for querying a single factory, and the 'of' parameter guidance explains how to request multiple aspects at once. However, there is no explicit 'when not to use' or comparison with alternative tools, so it stops short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lukszi/SatisfactoryMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server