Good Earth

Goodearth Tree Suitability

goodearth_tree_suitability

Whether a tree survives and gets its chill on this ground.

A tree is not asked "does it finish before frost" — that is a question only something that must finish in one season can be asked. It is asked two others, both settled before it goes in the ground:

Will it survive? Every winter on record has a coldest night; a cultivar has a limit. The answer is how often the first went below the second.
Will it fruit? A deciduous fruit tree needs chill hours to break dormancy cleanly. The answer is how many winters on record delivered them.

Both come back as a FREQUENCY across the record rather than a yes. A tree that survives nine winters in ten is a different proposition from one that survives five, and any single word hides the difference.

Chill is counted as hours in the 32-45 °F band between 1 November and 15 February — the window the published chill-hour figures were derived against. A wider window would bank more hours against a requirement calibrated to a narrower one and report a tree comfortable where it is not.

The requirements are yours. Hardiness limits and chill hours are cultivar figures that vary widely within a species; Good Earth computes what this ground delivered against them and does not publish agronomy.

Input Schema

TableJSON Schema

Name	Required	Description
`npub`	No	Required. Your Nostr public key (npub1...) for credit billing.
`block`	Yes	The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the error lists them with their ids. Blocks may overlap; each answers for its own ground. Save one with block_save first; geometry travels once, not on every call.
`trees`	Yes	The trees to judge, with the figures from their nursery tags. Each is {"tree": "Honeycrisp apple", "chill_hours": 800, "hardy_to_f": -30} with optional "category" and "emoji". Both figures are optional: a tree with neither is recorded and reported as unrated rather than refused.
`dpop_token`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does substantial work: it discloses that results are frequencies rather than yes/no answers, defines the exact chill-hour band and date window, and clarifies that hardiness/chill requirements are user-supplied cultivar figures. It does not explicitly state whether the call has side effects, but 'computes what this ground delivered' and the overall query framing make read-only behavior reasonably clear.

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 well organized with bolded questions and bullets, making the two core evaluative axes easy to scan. It is longer and more rhetorical than strictly necessary, with phrases like 'gets its chill on this ground' and the extended frost/frost finish framing adding flavor rather than operational precision, but each paragraph contributes meaningful conceptual context.

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?

Given that an output schema exists and parameter mechanics are covered in the input schema, the description is nearly complete for an agent: it explains calculation semantics, historical-record frequency, chill-window constraints, and the user's responsibility for cultivar figures. The only notable gap is the lack of explicit routing guidance against nearby sibling tools and an explicit read-only/no-side-effects statement.

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 description coverage is 75%, so the schema already documents block, trees, and npub. The main description adds real parameter meaning by defining how chill_hours should be counted (32–45 °F, November 1–February 15) and what hardy_to_f represents (the cultivar's coldest-night limit compared against the record). This goes beyond the schema fields.

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 frames the tool as judging whether a tree cultivar will survive and receive sufficient chill on a specific block, and it explains the survival/fruit questions with specific frequency-based answers. It distinguishes itself from one-season/crop tools via the 'does it finish before frost' contrast, though it never names a sibling tool directly. A crisper imperative like 'returns suitability frequencies for tree cultivars' would make the operation fully explicit.

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?

The description implies when to use this tool: when assessing perennial fruit trees against a saved block, and it implicitly excludes annual crops that must finish before frost. However, it does not explicitly name alternatives such as goodearth_crop_suitability or goodearth_tree_year, and the block-save prerequisite appears only in the input schema rather than the main description.

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

All Good Earth 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.