Skip to main content
Glama

collected_from_world

Find out which collectibles are still unclaimed in your world, with exact locations and the nearest ones from your position.

Instructions

Map collectibles: how many exist, how many you took, what is left and what is closest.

Slugs, somersloops, Mercer spheres and their shrines, mushrooms, drop pods and the loot caches around them. Two sources, and neither is asked the other's question:

  • the map says what exists and where, read from the installed game's own cooked packages, so placed is exact and every coordinate is exact;

  • the save says what is gone. The world is not saved -- a save never mentions a slug still lying there -- so its destroyed-actor list is the collected list, and it is exact too. remaining is the subtraction of the two.

Modes: census (default) counts every category; collected and remaining list individual placements with coordinates; nearest lists the remaining ones by distance from near, defaulting to the player.

A placement in a cell no save has ever loaded is counted as remaining and reported as never_streamed. It is never called present -- the map says where it is and nothing on disk says whether it is still there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNocensus | collected | remaining | nearestcensus
nearNoorigin for mode=nearest: 'x,y' in metres, 'me', or a factory name. Defaults to where the player is standing
saveNo
groupNoone category, e.g. 'power_slug_blue'. Omit to see them all
limitNomax rows (hard cap 25)
worldNo
Behavior5/5

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

The description discloses how data is derived from the map and save files, explains the exactness of coordinates, the subtraction logic for remaining, and the never_streamed edge case for unloaded cells. This is substantial behavioral context, especially given there are no annotations.

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 well-structured with a lead summary, bullet points for data sources, and clear mode explanations. Every section adds necessary context for a complex tool with six optional parameters, and the front-loaded summary immediately conveys the core purpose.

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 tool with no output schema, the description explains what each mode returns (counts, lists with coordinates, distance-ordered lists) and mentions key fields like placed, remaining, and never_streamed. Some output shape details remain unspecified, but the behavioral coverage is thorough given the tool's complexity.

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?

The schema already describes mode, near, group, and limit. The description adds meaningful semantics for mode (defines each mode) and near (defaults to player), but leaves save and world parameters unexplained despite them lacking schema descriptions. With 67% schema coverage, the description only partially compensates for the undocumented parameters.

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 maps collectibles (slugs, somersloops, Mercer spheres, mushrooms, drop pods, loot caches) and reports counts, collected, remaining, and nearest. The verb 'Map' plus the specific resource categories distinguish it from siblings like 'somersloops' which likely focuses on a single category.

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 explains the available modes (census, collected, remaining, nearest) and their defaults, providing clear context on how to invoke different behaviors. It does not explicitly name alternatives or say when not to use this tool, but the purpose is specific enough to guide selection.

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