Skip to main content
Glama

What grows in a place's climate

what_grows_here
Read-onlyIdempotent

Crops ranked by how well a town's or a map point's climate suits them (0–100), with what limits each, whether it needs irrigation, and the growing climate: hardiness zone, frost dates, chill hours, rain, dry season. Climate only: no soil, pests or markets.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
limitNoMax crops. Default 15
placeNoTown. Or pass lat and lon for any land point
categoryNoOnly one kind of crop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds real substance beyond them: the 0–100 ranking scale, that each crop comes with its limiting factor, irrigation need, and climate details (zone, frost dates, chill hours, rain, dry season), plus the explicit data-scope boundary.

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?

A single front-loaded sentence delivers the operation, the output shape, and the scope boundary with no filler. The final "Climate only" clause is short and high-value rather than padding.

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 must explain returns, and it does so thoroughly, down to the individual climate attributes. The one gap is that it does not state that lat and lon are supplied together for a map point, though the schema covers this.

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 60%, and the description usefully clarifies the two input modes — a town name versus a map point — which is the main ambiguity in the schema. It says nothing about the limit or category parameters, so it neither compensates for the uncovered third nor adds meaning the schema lacks.

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?

"Crops ranked by how well a town's or a map point's climate suits them (0–100)" names a specific verb (rank), resource (crops), scoring scale, and input modes (town name or coordinates). The trailing list of returned attributes and the "Climate only" scoping line separate it from siblings like list_crops or get_climate.

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 definition gives clear context for use: a town name or a lat/lon land point, with an explicit exclusion of soil, pests, and markets, which tells an agent when this tool is the wrong choice. It stops short of naming a sibling (e.g. where_to_grow or list_crops) as the alternative when a different question is asked.

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.

Resources