Skip to main content
Glama

Where a crop grows best

where_to_grow
Read-onlyIdempotent

Where in the world a crop (or one variety) suits the climate: land area that fits well, the best regions and countries, the best-fitting towns, and what stops it elsewhere. Scored on a 0.125° land grid. Climate only.

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": {
      "crop": "<crop>"
    },
    "name": "where_to_grow"
  }
}

Input Schema

NameRequiredDescriptionDefault
cropYesCrop slug from list_crops, e.g. avocado
varietyNoVariety slug from list_crops. Default: the best variety at each place

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are scored on a 0.125° land grid and are climate-only, which tells the agent the spatial resolution and the exclusions from the answer.

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 carries purpose and return shape, followed by two short qualifiers for grid resolution and scope. Every clause maps to either what the tool does or how to read its answer; nothing is filler.

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 does the work of describing returns by naming the four result components, and the two parameters are fully specified in schema. The remaining gap is minor: units or scale for 'land area that fits well' and the scoring scale are never stated.

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 both parameters are already documented, including the variety default. The description echoes the crop/variety distinction and 'one variety' framing but adds no syntax, format, or resolution detail beyond the schema, so the baseline 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 resource and direction: a crop (or one variety) mapped to where it suits the climate, and enumerates the outputs (land area, best regions and countries, best-fitting towns, limiting factors). This implicitly separates it from the inverse place-to-crops sibling, but no sibling is named explicitly, so an agent must infer the routing rather than read it.

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?

There is no explicit when-to-use or when-not guidance and no named alternative. Usage is only implied by the framing plus the closing constraint 'Climate only', which hints that non-climate suitability questions are out of scope but never says which tool handles them.

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