Skip to main content
Glama

Find medical cannabis brands

find_brands
Read-onlyIdempotent

Find the brands that make cannabis-based medicines, by name or dose form, with their listed product counts. Example: {"query":"Tilray"}

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

Input Schema

NameRequiredDescriptionDefault
sortNoDefault name_asc.
limitNoDefault 10.
queryNoBrand name.
offsetNoRows to skip.
categoryNoMakes this dose form.

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. Changed9 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 / results / items / properties / productCount / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / results / items / properties / productCount / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / total / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / total / minimum
      Added value: +-9007199254740991
  2. Changed5 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Only brands with a listed product in this dose form. CARTRIDGE is a vape cartridge."New value: +"Makes this dose form."
    • 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: -"Brand name, matched as text. Omit to browse."New value: +"Brand name."
    • changedInput schema / properties / sort / description
      Previous value: -"name_asc (default), name_desc, or products_desc (most listed products first)."New value: +"Default name_asc."
  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. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare this as read-only, idempotent, non-destructive, and not open-world. The description adds that results include listed product counts and that brands can be searched by name or dose form, but it does not add much operational context beyond that.

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?

The description is a single front-loaded sentence plus a compact example. Every element earns its place by stating the resource, filters, returned counts, and a sample invocation.

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 rich schema coverage, annotations, and an output schema, the description provides enough to call the tool correctly. The main remaining gap is sibling routing, especially when to use this versus get_brand or find_products.

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 description coverage is 100%, so the baseline is 3, but the description adds a concrete query example and clarifies the name/dose-form filtering concept. It still leaves sort, limit, and offset semantics to the schema, which is acceptable given full coverage.

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 gives a specific verb and resource: finding cannabis medicine brands, with scope including name or dose form and product counts. It is clear enough to separate from a product finder, but it does not explicitly differentiate against singular brand lookup or other sibling tools.

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 implied by 'Find the brands... by name or dose form' and the example query, suggesting a search/list use case. However, there is no explicit when-to-use guidance versus get_brand or find_products, and no exclusions or prerequisites are stated.

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.