Skip to main content
Glama

Good Earth

Goodearth Tree Year

goodearth_tree_year

When spring reached this ground, and what the sap did.

First leaf and first bloom, from USA-NPN's Spring Index, dated for this block and set against its own thirty-year normal. "Spring is early this year" is a headline; "leaf-out reached this block seven days before its normal" is something to act on.

First bloom is also when the pollen starts. That is a restatement of what bloom is, not a pollen forecast — Good Earth has no pollen feed, models none, and says nothing about what anyone should do about it.

The sap run, for a block with maple, birch or walnut on it. Sap moves on freeze and thaw rather than on warmth: a night below freezing followed by a day above it. Counted off this ground's own season record, so it costs no extra call. A block with nothing tappable gets no sap section — the count would be just as true there and would answer a question nobody on that ground asked.

The trees are read from the block's own record; nothing needs passing.

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

A3.9/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 it well: it discloses the data source, the comparison to a 30-year normal, the explicit statement that this is not a pollen forecast, the absence of pollen models, conditional output sections, and that all data comes from the block's own record with nothing else to pass.

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?

Bold section headers and a clear opening line make the structure easy to scan. Some prose is ornate and the pollen caveat is repeated, but each section earns its place by explaining meaningful behavioral nuance.

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?

An output schema exists, so return values do not need explanation. The description covers data source, baseline comparison, conditional sections, and the input model. It does not address how this tool relates to seasonal siblings, but that is not required to invoke it 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 schema already documents npub and block in detail, and the description adds that tree data is read from the block record so nothing else needs passing. However, 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.

Purpose4/5

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

The description clearly identifies the tool's purpose: reporting when spring reached a saved block (first leaf, first bloom, sap run) using USA-NPN Spring Index data compared to the block's own 30-year normal. It names the specific resource (a block) and the kind of answer, but does not explicitly distinguish it from related sibling tools.

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 context is implied rather than stated: it describes what the tool reports and notes conditional sections like the sap run only applying to blocks with maple, birch, or walnut. It gives no explicit when-to-use guidance or alternatives among the many sibling 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.