Skip to main content
Glama

Last Frost Date and Hardiness Zone MCP

USDA plant hardiness zone by ZIP code

hardiness_zone
Read-onlyIdempotent

The USDA plant hardiness zone for a US ZIP code from the 2023 USDA Plant Hardiness Zone Map (for example 6a), the average annual coldest winter temperature range it stands for in F and C, and the ZIP's coordinates. Answers "what growing zone am I in".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zip": "<zip>"
    },
    "name": "hardiness_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code, for example "80202" or "05401".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the description's job is to add context, which it does by naming the data source and vintage (2023 USDA Plant Hardiness Zone Map) and disclosing what the answer contains. It does not mention error behavior for invalid or non-US ZIPs, which would have pushed it higher.

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 definition is one dense sentence that front-loads the resource and then enumerates the outputs, followed by a short intent phrase. Nothing is padded, though the main sentence is long and stacks several clauses, which slightly reduces scannability versus splitting the return fields out.

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?

With no output schema, the description must convey return values, and it does: zone label, temperature range in both F and C, and coordinates. For a single-parameter read-only lookup with full annotation coverage, no information an agent needs in order to call it correctly is missing.

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% and the single parameter is fully documented, so the baseline is 3. The description earns above baseline by scoping the input to US ZIP codes specifically, which tells the agent the tool will not resolve non-US postal codes — a constraint the schema itself only implies via the example values.

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?

States a specific resource (USDA plant hardiness zone) tied to a specific input (US ZIP code) and enumerates the return payload: zone label like 6a, the coldest-winter temperature range in F and C, and coordinates. A single verb-plus-resource statement is unambiguous and an agent can match it to a 'what growing zone am I in' request without inspecting the schema.

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?

The closing sentence 'Answers "what growing zone am I in"' anchors the tool to a concrete user intent and the ZIP-code framing makes the applicability clear. It stops short of naming alternatives such as frost_dates or planting_calendar or stating when a different sibling is preferable, so explicit exclusions are absent.

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.