rust.wiki

Plan a loot room: which item categories go in which box, with each box's filter

plan_loot_room

Read-onlyIdempotent

Plan a loot room: which item categories go in which box, with each box's filter. The conveyor page's loot-room planner: each category needs (its item types x fill) slots; categories go biggest first into the tightest box they fit, spilling across the emptiest boxes when none is big enough. Each box gets the conveyor filter_json for its categories; not_enough_room says what didn't fit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_loot_room"
  }
}

Input Schema

Name	Required	Description
`fill_pct`	No	How much of each category you'll keep, % of its item types.
`categories`	No	Categories to store (default: everything but food, fun and attire).
`large_boxes`	No	Large Wood Boxes (48 slots).
`small_boxes`	No	Small Wood Boxes (18 slots).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable behavioral detail beyond annotations: the slot-filling algorithm, spillover behavior, per-box filter_json output, and not_enough_room reporting.

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 front-loaded with the purpose and then explains the algorithm and outputs in three dense but useful sentences. The first sentence largely restates the title, but the rest adds real value.

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 read-only planner with four documented parameters and no output schema, the description sufficiently explains the algorithm and names the key return fields. Minor gaps remain around exact return structure, but the definition is complete enough to invoke correctly.

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 100% and all four parameters have descriptions. The description adds the useful slot formula for fill, but does not substantially extend parameter meaning beyond what the schema already provides.

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: planning a loot room by assigning item categories to boxes with per-box filters. It clearly describes the planner behavior and distinguishes this tool from a generic conveyor-filter utility.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful context as the conveyor page's loot-room planner, but it does not explicitly say when to use this versus siblings like build_conveyor_filter or plan_farm, nor does it state exclusions.

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

All rust.wiki tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?