rust.wiki

Doors, walls and deployables ranked by sulfur to raid vs build cost

get_best_defences

Read-onlyIdempotent

Doors, walls and deployables ranked by sulfur to raid vs build cost. The data behind https://rust.wiki/building/best-value. doors, walls (walls, foundations and floors at every grade) and other (raidable deployables), each hardest to raid first. Every row has slug, name, health, raid - the cheapest single standard explosive (rockets, C4, satchel charges, explosive 5.56 ammo, beancans) as explosive (shortname), count and sulfur - and build, resource name -> amount (a building block's upgrade cost at its grade, a door's or deployable's crafting recipe). Building blocks add grade and type; doors and deployables add shortname, icon_url and url. explosives names the shortnames. Raid data cached for 24 hours.

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": "get_best_defences"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in operational detail. It supplies exactly that: the 24-hour raid-data cache (freshness expectations) and the exact result-shape breakdown per category. It does not mention result size or whether the whole dataset is returned in one call, which would complete the picture.

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 summary sentence is front-loaded and the payload URL is a useful anchor. The bulk is a dense field-by-field spec of the return structure, which earns its place given no output schema exists, though the run-on sentence listing explosive types is harder to parse than a short enumerated list would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of explaining return values — and it does, enumerating every row field (slug, name, health, raid.explosive/count/sulfur, build) and the per-category extras (grade/type for blocks, shortname/icon_url/url for doors and deployables). Combined with the caching note and category list, an agent has everything needed to call it with no arguments and interpret the response.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly focuses its effort on output semantics instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete resource (doors, walls, deployables) and the ordering criterion (sulfur to raid vs build cost), plus names the wiki page the data backs. An agent can tell it is a ranked-value dataset rather than a calculator. It stops short of naming siblings like get_raid_costs or calculate_raid_cost, so differentiation is inferential rather than explicit.

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?

Usage is implied by the content description — an agent can work out this is the tool for 'which building blocks are cheapest to raid relative to their cost' — and the 'hardest to raid first' ordering hints at how to read results. However, there is no explicit statement of when to use this versus get_raid_costs, calculate_raid_cost or get_building_piece, and no exclusions are given.

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?