Skip to main content
Glama
Sign In

rust.wiki

by wiki.rust
OverviewDiscussionsAdmin

Build cost, daily upkeep and raid cost of a base

calculate_base_cost
Read-onlyIdempotent

Build cost, daily upkeep and raid cost of a base. The base cost calculator page's math (https://rust.wiki/calculators/base). build_cost is the total resources (a block's upgrade cost at its grade, a door's crafting recipe); upkeep is the tool cupboard's daily and weekly cost on the building blocks at Rust's default brackets (the same result as /calculators/upkeep/compute); raid_path gives each layer's cheapest standard explosive and the total sulfur to reach the loot. unknown lists inputs that matched nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pieces": "<pieces>"
    },
    "name": "calculate_base_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
piecesYesComma-separated `slug:count` pieces: building blocks by grade slug from /building (`stone-wall`, `metal-foundation`...) and doors or deployables by slug or item shortname (`door.hinged.metal`). Display names work too.
raid_pathNoOptional: the layers a raider breaks through from outside to the loot, in order, same naming as `pieces` (`:n` repeats a layer).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description goes further by defining what each returned field means (`build_cost`, `upkeep` at default brackets, `raid_path` cheapest standard explosive plus total sulfur, `unknown` for unmatched inputs), which matters because no output schema exists.

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 first sentence front-loads the three outputs, then the description breaks each field into a labeled clause. It is dense and relies on backtick labels, but every sentence carries information; the URL reference is the only borderline filler.

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?

For a two-parameter, read-only calculator with no output schema, the description supplies exactly what is missing: the meaning and units of every returned field plus the caveat that `unknown` lists unmatched inputs. An agent can call it and interpret the result without further context.

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%, so both `pieces` and `raid_path` are already documented with format, examples, and naming conventions. The description adds only the detail that `raid_path` is the layers a raider breaks through in order and that `:n` repeats a layer — modest but real value beyond the schema.

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 specific composite resource: build cost, daily upkeep, and raid cost of a base, and ties it to the referenced calculator page. It implicitly separates the bundled result from the more granular sibling endpoints (`/calculators/upkeep/compute`), but never names `calculate_upkeep` or `calculate_raid_cost` directly, so sibling differentiation is left partly to inference.

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 through the output breakdown (`unknown` listing unmatched inputs) and the note that `raid_path` is optional, which hints at two calling modes. There is no explicit statement of when to prefer this combined calculator over the sibling single-purpose tools (`calculate_upkeep`, `calculate_raid_cost`), and no exclusion guidance.

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

All rust.wiki toolsInspect
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