Skip to main content
Glama
Sign In

rust.wiki

by wiki.rust
OverviewDiscussionsAdmin

Raw materials to craft a list of items

calculate_craft_cost
Read-onlyIdempotent

Raw materials to craft a list of items. Resolves every recipe down to raw materials, per unit (items made in batches, like gunpowder, are divided by their batch size), exactly as the craft calculator page does. raw_materials is the total, largest first; items echoes each input with its direct recipe; unknown lists inputs that matched no item.

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": {
      "items": "<items>"
    },
    "name": "calculate_craft_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesComma-separated `shortname:quantity` pairs (display names work too; quantity defaults to 1).

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 and closed-world, so the safety profile is covered. The description still adds genuine behavioral context beyond the annotations: batch-size normalization for crafted outputs like gunpowder, per-unit semantics, and the shape of the three result keys including the 'unknown' bucket for unmatched inputs. Return structure is the main added value, though there is no note on how large inputs are handled.

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 core behavior is front-loaded in the first clause, and the three result keys are enumerated compactly with backticks. It is slightly dense with parenthetical asides, but no sentence is 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 one-parameter, read-only calculation tool with no output schema, the description supplies everything an agent needs: input format is in the schema, per-unit and batch semantics are explained, and all three return keys are described. No material gap remains.

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 description coverage is 100% and the single 'items' parameter is fully documented in-schema (comma-separated shortname:quantity, display names accepted, quantity defaults to 1, plus an example). The description adds only the phrase 'a list of items' and the echo behavior in the result, so per the baseline rule a 3 is correct when the schema carries the parsing contract.

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 operation: resolve every recipe for a list of items down to raw materials, per unit, with batch division matching the craft calculator page. That is far more than the title restates, and an agent can tell it is a crafting-cost calculator rather than a loot or raid calculator. It never names the nearby alternatives (calculate_raid_cost, calculate_recycle_yield) explicitly, so sibling differentiation is left implicit.

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 rather than stated: 'to craft a list of items' and 'exactly as the craft calculator page does' tell the agent this mirrors the in-game crafting calculator. There is no explicit when-to-use or when-not, and no routing to calculate_raid_cost or calculate_recycle_yield for cost questions involving raiding or recycling.

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