Skip to main content
Glama

Search supplier research leads

search_supplier_research
Read-onlyIdempotent

Search company-published botanical supplier research. Every result is an unconfirmed research lead with a source URL and outstanding evidence checks. No stock, price, sample or quote availability is implied.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
ingredientNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations establish a read-only, idempotent, non-destructive operation, and the description adds trust-level context beyond them: every result is an unconfirmed research lead with a source URL and outstanding evidence checks, and no availability is implied. That materially helps an agent interpret and caveat the results.

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?

Three short sentences, front-loaded with the purpose, then the nature of results, then the availability caveat. No filler, and each sentence adds a distinct fact.

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?

There is no output schema, so the description usefully explains what a result contains, but it omits pagination semantics (limit max 20, offset max 10000) and how query and ingredient interact. Adequate for a read-only search but not 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 four parameters, and the description never explains query, ingredient, limit or offset. It does not compensate for the coverage gap, so an agent must rely on parameter names alone to distinguish the free-text query from the ingredient filter.

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 opens with a concrete verb and resource: search company-published botanical supplier research. That is specific enough to separate it from search_ingredients and the cost calculators, though it does not name a sibling alternative 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?

Guidance is implied rather than stated: an agent can infer this is for finding supplier research leads, and the closing sentence warns that stock, price, sample or quote availability is not implied, which is a partial when-not. No explicit alternative or prerequisite is 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.