Skip to main content
Glama

List / filter cultivars

list_strains
Read-onlyIdempotent

Meaning-aware search over the 340-cultivar encyclopedia, ranked by relevance. Free-text 'q' understands phrases like "short flowering", "high yield", "purple strains", "gas", "OG lineage", "Zkittlez terp profile", "Prime Cuts exclusives", or a breeder name; the same meanings are available as explicit filters. Every result carries 'matched_on' (the factual fields it matched) and the response carries 'interpreted' (how q was read). Nothing is inferred beyond the documented record. Each result includes a 'menu' block with a live-availability URL when Prime Cuts sells the cultivar.

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_strains"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree text: strain/alias/lineage/breeder names or descriptive phrases (aroma, colour, flowering speed, yield, exclusives)
typeNo
colorNoReported flower colour, e.g. 'purple'
limitNo
yieldNoMinimum documented yield rating
flavorNoAroma/flavour/terpene keyword with synonyms, e.g. 'gas' (fuel, diesel), 'candy', 'citrus'
offsetNo
breederNoBreeder slug from list_breeders, e.g. 'seed-junky-genetics'
lineageNoName that must appear in the lineage or ancestry, e.g. 'OG', 'Zkittlez', 'Gelato'
on_menuNotrue = only cultivars Prime Cuts sells as clones
terpeneNoDominant terpene, e.g. 'limonene'
exclusiveNotrue = only cultivars bred or pheno-hunted in-house by Prime Cuts Nursery
terp_profile_ofNoStrain name/slug: return cultivars that share its dominant terpene or descend from it
flowering_max_weeksNoDocumented flowering time at most this many weeks (e.g. 8 for fast finishers)
flowering_min_weeksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restating. The description adds real value beyond that with 'matched_on' per result, 'interpreted' in the response, the no-hallucination guarantee, and the live-availability 'menu' block. That is solid, though it does not cover pagination behavior or result ordering beyond 'relevance'.

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?

Front-loads the core purpose in the first sentence, then layers query semantics, result-trust fields, and the menu block. The example-phrase list is long but each example disambiguates a different filter dimension, so it earns its space. Minor redundancy between 'the same meanings are available as explicit filters' and the earlier phrase list.

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 15-parameter search tool with no output schema, the description compensates well by describing the response shape (matched_on, interpreted, menu/availability URL) and the ranking guarantee. Pagination and the total-result/count behavior are left unstated, which is a small but real gap for an agent paging through 340 cultivars.

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

Parameters4/5

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

Schema coverage is 73% across 15 parameters, so the schema does much of the work, but the description adds meaning the schema cannot: q is meaning-aware and accepts descriptive phrases, and those same meanings are exposed as explicit filters so the agent can choose structured params over free text. Concrete phrase examples ('short flowering', 'OG lineage', 'gas') clarify how fuzzy the q surface is. It does not touch limit/offset or terp_profile_of semantics, leaving some gap.

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 verb and resource with concrete scope: 'meaning-aware search over the 340-cultivar encyclopedia, ranked by relevance.' An agent immediately knows this is the cultivar search/filter endpoint. It stops short of naming how it differs from sibling get_strain (single-record lookup) or the generic search tool, so it is clear but not sibling-differentiated.

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?

The description explains how to use the tool (free-text q with natural phrases, or the equivalent explicit filters), which is genuine usage guidance for choosing between modes. However, it never states when to prefer this over get_strain for a single cultivar or over the generic search sibling, so tool-selection guidance is only implied.

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