Skip to main content
Glama

rank_unlocks

Measure the worth of each locked alternate recipe against your current plan by solving with and without it, identifying which hard drive unlocks actually improve your setup.

Instructions

What every locked alternate recipe would be worth to THIS plan.

One counterfactual per candidate: solve the plan, solve it again with the recipe added, report the difference. It answers "which unlock should I chase" with a number in the plan's own units instead of a tier list, because a recipe's worth depends entirely on what you already have.

A zero is an answer. Most candidates change nothing, and "you are not missing anything here" is a decision -- it is otherwise reached by walking the recipe tree by hand.

Deltas are an UPPER bound: a candidate needing a machine you have not built is judged as if you had it, and the machine is named. Alternates currently offered by a pending hard drive are flagged, which is the difference between "worth having" and "claimable now".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNorecall a saved plan by name
saveNo
limitNomax rows (hard cap 25)
worldNo
clocksNo
searchNoonly test alternates whose name matches
sloopsNo
exportsNo
sourcesNo
objectiveNomax_mw
allow_sinksNo
target_itemNo
only_recipesNo
exclude_recipesNo
export_minimumsNo
machine_cost_mwNo
only_free_nodesNo
extractor_clocksNo
water_extractorsNo
Behavior5/5

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

With no annotations, the description compensates thoroughly: it explains that deltas are upper bounds, that unbuilt machines are assumed available and named, that pending hard-drive alternates are flagged, and that a zero result is meaningful. This is exceptional behavioral disclosure.

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 appropriately sized for the tool's complexity, with each sentence adding unique behavioral context. It is front-loaded with the core purpose and logically structured, making it easy to follow.

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?

The description conveys the output concept (a number per unlock) and covers edge cases like zero and upper bounds, which is useful given the absence of an output schema. However, with 19 parameters and no annotations, the lack of parameter guidance makes it incomplete for correct invocation.

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

Parameters1/5

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

Schema description coverage is only 16% (3 of 19 parameters), yet the description adds no parameter-level guidance. It references 'this plan' but does not explain save, world, clocks, sources, objective, or other parameters, failing to compensate for the schema gap.

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 clearly states the tool ranks locked alternate recipes by their value to the current plan, answering 'which unlock should I chase' with a quantitative difference. It distinguishes itself from a tier list, making the purpose specific and unambiguous.

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 description explicitly frames the use case as deciding which unlock to chase and explains why a tier list is inadequate. However, it does not name specific alternative tools or provide explicit when-not-to-use conditions.

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