Skip to main content
Glama

List crops

list_crops
Read-onlyIdempotent

The crops and varieties Climatch scores, with the slugs what_grows_here and where_to_grow use.

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

Input Schema

NameRequiredDescriptionDefault
qNoFilter by name, e.g. 'grape' or 'avocado'
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds only the fact that records carry slugs consumed by sibling tools; it says nothing about ordering, result size, or whether the full catalog is returned when no filter is given.

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?

A single front-loaded sentence with no padding, and the cross-reference to sibling tools earns its place. The grammar ('the slugs what_grows_here and where_to_grow use') is awkward enough to slow parsing slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with annotations covering the safety profile and no output schema, this is borderline adequate. Missing is any indication of the returned record shape (slug plus display name) or default behavior when q and category are both omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: q is documented in the schema but category is a bare enum, and the description mentions neither parameter. With half the parameters undescribed, the description should compensate for the gap and does not, leaving category semantics to be inferred from the enum values alone.

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 the resource (crops and varieties Climatch scores) and identifies the key returned token, the crop slug, so an agent can tell this is the crop catalog endpoint. It lacks an explicit verb but the noun phrase defines the resource clearly against siblings like what_grows_here.

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 via a dependency hint: the returned slugs are what what_grows_here and where_to_grow consume, which suggests calling this first to resolve a crop. There is no explicit when-to-use, when-not-to-use, or statement about how it differs from other listing options.

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