Skip to main content
Glama

Find cannabis strains

find_strains
Read-onlyIdempotent

Find strain profiles by name or genetics, with THC/CBD ranges. No effects or medical uses are published. Example: {"genetics":"Hybrid"}

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
queryNoStrain name or nickname.
offsetNoRows to skip.
geneticsNoStrain type.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageNoWhich window of 60 directory rows this answer read
totalYesHow many matched in all; narrow the query when this exceeds the results
resultsYes
directoryTotalNoThe whole directory, when the tool read one window of it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / directoryTotal / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / directoryTotal / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / page / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / total / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / total / minimum
      Added value: +-9007199254740991
  2. Changed4 schema fields changed
    • changedInput schema / properties / genetics / description
      Previous value: -"The strain type: Indica, Sativa or Hybrid."New value: +"Strain type."
    • changedInput schema / properties / limit / description
      Previous value: -"How many to return, 1-25. Default 10."New value: +"Default 10."
    • changedInput schema / properties / offset / description
      Previous value: -"Skip this many results, for the next page (the answer says which offset comes next). Default 0."New value: +"Rows to skip."
    • changedInput schema / properties / query / description
      Previous value: -"Strain name or nickname, e.g. \"Gelato\". Omit to browse."New value: +"Strain name or nickname."
  3. Changed2 schema fields changed
    • addedOutput schema / properties / directoryTotal
      Added value: +{
      +  "description": "The whole directory, when the tool read one window of it",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / page
      Added value: +{
      +  "description": "Which window of 60 directory rows this answer read",
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Skip this many results, for the next page (the answer says which offset comes next). Default 0.",
      +  "maximum": 500,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  5. Changed6 schema fields changed
    • changedInput schema / properties / genetics / description
      Previous value: -"Indica, Sativa or Hybrid."New value: +"The strain type: Indica, Sativa or Hybrid."
    • addedInput schema / properties / genetics / enum
      Added value: +[
      +  "Indica",
      +  "Sativa",
      +  "Hybrid"
      +]
    • changedInput schema / properties / limit / description
      Previous value: -"Default 10."New value: +"How many to return, 1-25. Default 10."
    • changedInput schema / properties / query / description
      Previous value: -"Strain name."New value: +"Strain name or nickname, e.g. \"Gelato\". Omit to browse."
    • addedInput schema / properties / query / maxLength
      Added value: +120
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "note": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "cbdPercent": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "genetics": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "thcPercent": {
      +            "description": "A figure or a range, e.g. \"18-22\"",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "url": {
      +            "anyOf": [
      +              {
      +                "format": "uri",
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "Canonical Findabis page, absolute; null when the listing has no page"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "slug",
      +          "url",
      +          "genetics",
      +          "thcPercent",
      +          "cbdPercent"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "How many matched in all; narrow the query when this exceeds the results",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "total"
      +  ],
      +  "type": "object"
      +}
  6. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds real data-scope context beyond that: results carry THC/CBD ranges but no effects or medical-use fields, which tells the agent what it will and will not get back before calling.

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?

Two short sentences plus an example, front-loaded with the lookup capability and immediately followed by the key data-scope caveat. The embedded JSON example is slightly awkward inline but earns its place by showing enum usage.

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 an output schema present and 100% parameter coverage, the description need not explain return shapes and correctly focuses on scope and lookup modes. Only the missing find-vs-get routing keeps it from being fully complete for an agent choosing among directory search tools.

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 description coverage is 100%, so query, genetics, limit and offset are already fully documented, establishing a baseline of 3. The description reinforces that query and genetics are the two lookup modes and supplies a worked example for the enum, but adds no syntax or format detail the schema lacks.

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 (find strain profiles) and names the two lookup axes (name or genetics) plus the returned attributes (THC/CBD ranges). It is clearly separable from get_strain, though it never names that sibling explicitly.

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?

'No effects or medical uses are published' is a useful scope exclusion that stops an agent from searching here for effect data, and the example query implies a discovery pattern. However, there is no explicit routing guidance to the sibling get_strain for fetching a single known strain, so the when-to-use-vs-alternative piece is left implicit.

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.