rust.wiki

Every tea recipe: berries, Mixing Table slot order, buff and duration

get_tea_recipes

Read-onlyIdempotent

Every tea recipe: berries, Mixing Table slot order, buff and duration. The data behind https://rust.wiki/teas. Each tea has name, shortname, tier (Basic, Advanced, Pure), ingredients (item, qty, shortname), slot_order / slots (the Mixing Table order for Basic teas - order matters: Scrap and Warming Tea use the same berries), effect, duration_minutes and note (Advanced and Pure values predate Rust's 5 Nov 2026 tea nerf). notes covers stacking and mixing rules. Sourced from Facepunch's wiki and devblogs (sources, verified).

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_tea_recipes"
  }
}

Input Schema

Name	Required	Description	Default
`search`	No	Case-insensitive match on the tea's name or effect.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive lookup. The description adds valuable behavioral context beyond annotations, including the vintage caveat that Advanced and Pure tea values predate the 5 Nov 2026 nerf and that slot order matters for some teas.

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 dense but front-loads the core purpose and then enumerates returned fields and caveats efficiently. It is somewhat lengthy, but most sentences earn their place by clarifying data structure or limitations.

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 low-complexity lookup tool with no output schema, the description explains the returned fields, caveats, note coverage, and data sources thoroughly. An agent has enough context to call the tool 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?

The single search parameter is fully documented in the schema as a case-insensitive match on name or effect. The description does not add further search semantics, so the schema carries the parameter guidance.

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 clearly states that the tool returns every tea recipe, including berries, Mixing Table slot order, buff, and duration. It is specific to tea recipes and does not overlap with any sibling tool, though it does not explicitly contrast itself with alternatives.

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 'Every tea recipe' scope and the schema's search parameter, but the description does not explicitly say when to use this tool versus related resources like search_guides. No exclusions or alternatives are named.

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?