rust.wiki

Daily upkeep for a base

calculate_upkeep

Read-onlyIdempotent

Daily upkeep for a base. The upkeep calculator page's math: the block count walks Rust's default upkeep brackets to a blended daily rate, and each resource's daily upkeep is what was spent building times that rate (per_week = 7 days).

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": {
      "blocks": "<blocks>"
    },
    "name": "calculate_upkeep"
  }
}

Input Schema

Name	Required	Description
`wood`	No	Total wood spent building the base.
`stone`	No	Total stone spent.
`blocks`	Yes	Number of building blocks (foundations, walls, floors... each counts one).
`metal_fragments`	No	Total metal fragments spent.
`high_quality_metal`	No	Total high quality metal spent.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real value by disclosing the calculation model (default upkeep brackets, blended daily rate, per_week = 7 days), but it omits whether results assume vanilla brackets and what the response shape actually contains.

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?

Two tightly written sentences that front-load the purpose and then explain the math with no filler. The parenthetical about per_week is slightly tucked away but still earns its place.

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?

With no output schema, the description carries the burden of explaining returns and does so partially by defining the per_week field and the blended daily rate. It stops short of enumerating the full response or the bracket source assumption, which is the main remaining gap.

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 all five parameters are already documented with units ('total wood spent building', 'number of building blocks'). The description reinforces the inputs conceptually but adds no syntax, edge-case, or defaulting detail beyond the schema, so baseline 3 applies.

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?

States a specific computation: daily upkeep for a base, derived from block count via Rust's upkeep brackets and per-resource spend. The bracket-based math implicitly separates it from the rule-lookup sibling get_upkeep_rules, though it never names that sibling outright.

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 only implied by the recipe-like description ('blocks + amounts spent'). There is no explicit statement of when to call this versus get_upkeep_rules or calculate_craft_cost, and no caveats about vanilla vs server-specific brackets.

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?