Skip to main content
Glama

Search botanical ingredients

search_ingredients
Read-onlyIdempotent

Search CleanIngredients ingredient names, summaries and species notes. Includes core and later-stage research; returns status, source links and review dates. Empty query lists ingredients.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the burden is lighter. The description still adds real value beyond them by disclosing the returned fields (status, source links, review dates) and defining the empty-query behavior, which is exactly the kind of context annotations cannot convey.

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?

Three short sentences with the primary capability front-loaded and no filler. Every sentence carries information; the only mild weakness is that the coverage remark ("core and later-stage research") arrives before the more operationally useful empty-query note.

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?

With no output schema, the description does the right thing by enumerating return fields and noting review dates and source links. But for a search tool with paging parameters and no schema descriptions, the absence of any guidance on pagination limits or result-set size makes it only adequately complete.

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 description coverage is 0% for three parameters, so the description must carry parameter meaning. It only partially does: "Empty query lists ingredients" explains query's default, but limit and offset — including their bounds and pagination semantics — are never mentioned, leaving the majority undocumented in prose.

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 a specific verb and resource ("Search CleanIngredients ingredient names, summaries and species notes") and states the searched fields, so the scope is concrete. It stops short of explicitly distinguishing itself from the single-record sibling get_ingredient or the other search_* tools, so differentiation relies on the tool name alone.

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?

"Empty query lists ingredients" gives one useful usage path (browse-all) and "Includes core and later-stage research" hints at coverage breadth. However, there is no explicit statement of when to use this instead of get_ingredient or search_supplier_research, and no exclusions or prerequisites are given.

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.