rust.wiki

Plant grow time, clones per cut, yield bonus and water use

plan_farm

Read-onlyIdempotent

Plant grow time, clones per cut, yield bonus and water use. The farm planner page's maths (https://rust.wiki/calculators/farm-planner): time to ripe = the plant's base time / (1 + 25% per G), x1.5 unfertilized; stages splits it into Seed, Seedling, Sapling, Fruiting and Mature to ripe; yield_bonus_pct is +25% per Y; clones_per_cut adds one per two Y; water is per plant per tick, +10% per W. Harvests are relative (Facepunch publishes no base amounts). For the best gene layout use /calculators/genetics/best.

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

Input Schema

Name	Required	Description	Default
`count`	No	How many planters.
`genes`	No	The clone's six genes from G, Y, H, W, X.	GGGYYY
`plant`	No	Crop: hemp, corn, pumpkin, potato, wheat, sunflower, rose, orchid, red_berry, blue_berry, green_berry, yellow_berry, white_berry (or its name).	hemp
`planter`	No	Planter: planter.large, planter.small, planter.triangle, bathtub.planter, minecart.planter, plantpot.single.	planter.large
`fertilized`	No	Ground condition 100% (fertilizer). Unfertilized takes about half as long again.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description adds value by explaining output semantics and the important limitation that harvest amounts are relative because Facepunch publishes no base amounts. The G/Y/W formulas go beyond what annotations provide.

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 definition is dense but mostly earns its place through formulas and caveats. The opening sentence partly restates the title and could be reframed with a clearer verb, but overall it remains compact.

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 explains the main returned metrics and formulas plus the relative-harvest caveat. It is nearly complete for a read-only calculator, though it does not fully explain how the count parameter scales the outputs.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful gene semantics: +25% grow speed per G, +25% yield per Y, one extra clone per two Y, +10% water per W, and x1.5 growth time when unfertilized. Count and planter meanings are left to 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 makes clear this computes farm-planning metrics such as grow time, yield bonus, clones, and water use, with supporting formulas. It does not explicitly distinguish itself from sibling tools such as genetics_best_layout or genetics_predict, so it stops short of a 5.

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?

It implies use for farm planner math and points to /calculators/genetics/best for best gene layout, but that is an external URL rather than an explicit sibling tool or a when-not-to-use rule. No prerequisites or exclusions are stated.

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?