g4rden garden planner

Get a city's growing guide

get_city_guide

Read-only

A city's growing guide as Markdown: average last and first frost dates (from a nearby weather station where there is one), the frost-free season, hardiness zone, climate, and the crops that suit it.

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": {
      "city": "<city>"
    },
    "name": "get_city_guide"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	A slug from find_city (e.g. 'leeds') or a city name, optionally with its region or country ('Portland, Oregon').

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026

changedInput schema / properties / city / description

Previous value: -"A slug from find_city (e.g. 'leeds') or a city name."New value: +"A slug from find_city (e.g. 'leeds') or a city name, optionally with its region or country ('Portland, Oregon')."

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's job is lighter. It adds genuine context beyond them: the output format is Markdown, and frost dates come 'from a nearby weather station where there is one', which usefully warns that some cities may lack station-derived frost data. It does not say what happens for an unrecognized city, but the data-availability caveat is the more valuable disclosure.

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

Conciseness5/5

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

One sentence, no filler, and the most decision-relevant element (what the guide contains) is front-loaded immediately after the format declaration. Nothing could be removed without losing content.

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?

For a single-parameter, read-only lookup with no output schema, the description covers format and return content thoroughly, which is what an agent needs to decide relevance. Minor remaining gap: no statement of behavior for an unknown or ambiguous city, which matters given free-form name input.

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 single parameter has 100% schema description coverage, including the slug-from-find_city convention and the 'Portland, Oregon' disambiguation example. The description adds nothing about the city argument, so the baseline 3 applies – the schema does the work here.

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 opens with a specific resource – 'a city's growing guide as Markdown' – and then enumerates exactly what the guide contains: frost dates, frost-free season, hardiness zone, climate, and suitable crops. That is far more specific than the title alone, though it never names a sibling (e.g. what_to_plant or find_city) to sharpen the boundary.

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: an agent can infer this is the lookup for city-level climate/zone baseline data, but the description states no condition for choosing it over what_to_plant, get_plant, or find_city. No exclusions or prerequisites are given, so routing depends on inference from sibling names and the caller's schema.

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

All g4rden garden planner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?