g4rden garden planner

Find a g4rden city guide

find_city

Read-only

Find g4rden's growing guides by place name, or the nearest guides to a latitude/longitude. Returns slugs to use with the other tools. Covers 1,000+ cities worldwide.

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

Input Schema

Name	Required	Description
`lat`	No
`lon`	No
`query`	No	A city or town name, optionally with its region or country, e.g. 'Leeds', 'Portland, Oregon' or 'London, UK'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026

changedInput schema / properties / query / description

Previous value: -"A city or town name, e.g. 'Leeds' or 'Portland'."New value: +"A city or town name, optionally with its region or country, e.g. 'Leeds', 'Portland, Oregon' or 'London, UK'."

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds the return artifact ('slugs') and dataset scale, but says nothing about what happens when neither query nor coordinates are supplied (zero required parameters), or whether lat and lon must be passed together.

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?

Three short sentences, front-loaded with the primary action and followed by the return value and scope. No redundant or filler wording; every sentence carries information an agent would act on.

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 low-complexity read-only lookup with no output schema, the description covers purpose, both input modes, and the return format. The remaining gap is edge-case behavior — an empty call given zero required parameters, and coordinate/name precedence — which is minor but would matter to an agent composing arguments.

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 only 33% — only 'query' is documented in the schema. The description partially compensates by explaining that lat/lon drive a 'nearest guides' lookup, but it doesn't state the pairing requirement, precedence when both query and coordinates are given, or how 'nearest' is resolved at scale.

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 names a specific verb and resource ('Find g4rden's growing guides') and splits it into two clear modes: lookup by place name and nearest-match by latitude/longitude. It also states the return type ('Returns slugs to use with the other tools') and coverage ('1,000+ cities worldwide'), which distinguishes it from the sibling get_city_guide without naming it explicitly.

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?

It gives clear context for both invocation styles (place name vs. coordinates) and signals the downstream workflow by saying the returned slugs feed 'the other tools.' It stops short of naming which sibling to call next or stating when not to use this tool (e.g., when you already have a slug).

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?