Skip to main content
Glama

Last Frost Date and Hardiness Zone MCP

Frost forecast

frost_forecast
Read-onlyIdempotent

Forecast frost and freeze nights for the next 1 to 16 days (default 16) at a ZIP code, place or coordinates: each night at or below 36 F with its category (frost possible, frost or light freeze, freeze, hard freeze), the first night at or below 32 F and the coldest night. Answers "will it frost tonight".

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_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays ahead, 1 to 16. Default 16.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value beyond that by disclosing what the result contains (per-night categories, first night at or below 32 F, coldest night) and the forecast horizon with its default. It does not mention failure behavior for unresolvable place names, which is the main remaining gap.

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 verb, resource and horizon are front-loaded, then the detail is packed into a colon-led clause, so nothing is wasted. It is a single dense sentence with heavy parenthetical listing, which is slightly harder to scan than a two-sentence split but still efficient.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so precisely by naming each night's category tiers and the two summary values. Combined with the annotations covering safety and idempotency, only error and ambiguity handling for location resolution is left unaddressed.

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 100%, so all four parameters, their ranges, the default of 16 days and the accepted location formats are already documented in the schema. The description restates the same information without adding syntax or precedence details (for example, what happens if both location and lat/lon are supplied), so the baseline of 3 applies.

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?

States a specific verb and resource ("Forecast frost and freeze nights") plus the scope (next 1 to 16 days at a ZIP, place or coordinates) and the exact thresholds used (36 F and 32 F). The purpose is unmistakable, but it never distinguishes itself from the sibling frost_dates, which plausibly overlaps on frost-night information.

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 closing line "Answers 'will it frost tonight'" gives a concrete use case, and the default of 16 days is stated. However, there is no explicit when-not guidance and no routing to frost_dates or planting_calendar, so the agent must infer which tool handles historical frost dates versus forward-looking forecasts.

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.