Skip to main content
Glama

Last Frost Date and Hardiness Zone MCP

Last frost and first frost dates

frost_dates
Read-onlyIdempotent

Average (median) last spring frost date and first fall frost date for a US ZIP code, a place name or coordinates, the dates beaten in only 1 year in 10, the earliest and latest on record, the median frost-free growing season, and the last spring and first fall frost of the latest seasons. Computed from 30 complete seasons of daily minimum temperatures. threshold_f 32 (frost, default), 36 (light frost on tender plants) or 28 (hard freeze).

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

Input Schema

NameRequiredDescriptionDefault
latitudeNoLatitude, instead of location.
locationNoA US ZIP code ("80202"), a place ("Burlington, VT", "Leeds, UK") or "lat,lon". Add the state or country to a place name to avoid a same-named town.
longitudeNoLongitude, instead of location.
threshold_fNoFrost threshold in F: 32 (default), 36 or 28.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds genuine context beyond them: the data provenance (30 complete seasons of daily minimum temperatures) and what each threshold value physically means (32 frost, 36 light frost on tender plants, 28 hard freeze).

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?

Front-loaded with the primary result and tightly organized, with no filler sentences. The first sentence is a dense run-on catalog of eight return quantities, but since there is no output schema each item carries information the agent cannot get elsewhere.

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 appropriately enumerates what comes back (medians, 1-in-10 exceedance dates, records, season length) and how it is derived, which is enough to call the tool correctly. Minor gaps remain: date formatting/units and the behavior when no location or coordinates are provided.

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 3 is the baseline, and the description earns above that by giving the real-world meaning of the three threshold values, including that 32 is the default. It does not clarify what happens if no locator (location or lat/lon pair) is supplied, even though required parameters are zero.

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 states a specific resource (median last spring / first fall frost dates, record extremes, frost-free season length) and a specific basis (30 complete seasons of daily minimum temperatures). An agent can tell this is a climatological statistics tool rather than a live forecast, though it never names the siblings it differs from.

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 only implied: "Computed from 30 complete seasons" signals historical normals as opposed to a forecast, which indirectly separates it from frost_forecast, but there is no explicit when-to-use, when-not-to-use, or alternative named. An agent must infer the routing itself.

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.