Skip to main content
Glama

Good Earth

Goodearth Drying Window

goodearth_drying_window

When the dew burns off this ground, the dry days ahead, and the next rain.

Answers "is it dry enough yet?" for a grower planning to cut flowers, pick, mow or make hay. Returns this morning's and tomorrow morning's dew-off hour (the first hour the leaves are estimated to stay dry for two hours running), the first run of forecast days with no rain, the next hour of rain, and per day the rain, wet hours, reference evapotranspiration (FAO-56 ET0) and peak vapour-pressure deficit — how hard the air is pulling water out of anything wet. Ten days ahead, from one forecast call.

Not wet is not drying: a still, overcast, humid day wets nothing and dries little, which is why ET0 travels with every day. Wetness is ESTIMATED from modelled humidity and rain, never measured, as in disease_risk.

Conditions only. Good Earth never says a crop is ready to cut or that hay will cure — that depends on the crop, the swath and the field — and it publishes no agronomy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npubNoRequired. Your Nostr public key (npub1...) for credit billing.
blockYesThe 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.
dpop_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does this well. It discloses that wetness is ESTIMATED, never measured, that ET0 is included to explain drying, that this is 'Conditions only', and explicitly says Good Earth publishes no agronomy. It also defines the dew-off hour precisely.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is informative and every substantive paragraph earns its place, but the opening line is poetic rather than functional, so the core purpose is not front-loaded. It is longer than strictly necessary, though still well-organized into 'what', 'returns', and '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 complex forecasting tool with an output schema, the description is remarkably complete: it explains the question answered, the time horizon (ten days ahead), the per-day fields, the estimation caveat, and the scope boundary. Nothing needed to correctly invoke and interpret the result is missing.

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 67%, and the description adds no parameter-level meaning. The block and npub parameters are already well described in the schema, but dpop_token remains undocumented and the description does not compensate for that gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: it 'Answers "is it dry enough yet?"' for a grower planning to cut flowers, pick, mow or make hay, and lists the exact outputs (dew-off hours, dry-day runs, rain hour, ET0, VPD). This is clearly distinguishable from sibling window/frost tools by content even without naming them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit context for when to call the tool (grower planning to cut flowers, pick, mow or make hay) and clarifies limitations ('Conditions only'). However, it never explicitly names alternatives or tells an agent when not to use this tool versus related window tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.