Skip to main content
Glama

search_products

Read-onlyIdempotent

Search products offered by shops on Vaper.club. Each result is one shop's product record with brand, model, category, shop, price range, stock status, variants, rating and source URL (no internal product ids). Use when users ask to find, identify or research vape products. Provides objective product data and user feedback for adults only; it does not provide guidance on circumventing age verification, purchase restrictions or other legal limits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
shopNoOptional shop name.
queryYesProduct name, brand, model or search keywords. Required.
countryNoOptional ISO 3166-1 alpha-2 country code of the shop location.
sort_byNorelevance (default), latest, rating, reviews, price_asc or price_desc.
languageNoOptional language code.
page_sizeNoPage size, 1-20. Default 10.
brand_nameNoOptional brand name; recognized names are applied as a filter.
model_nameNoOptional model name.
category_nameNoOptional product category name or code.

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 readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful payload context (one shop's record per result, no internal product ids) but says nothing about pagination limits, result caps, or rate behavior beyond what the schema states. The closing sentence is a policy/eligibility note rather than a behavioral trait of the tool.

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?

The definition is front-loaded with purpose and result shape in the first two sentences, which is exactly what an agent needs first. The third sentence on adult-only use and legal limits is longer than the operational content and is only marginally relevant to correct 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 no output schema, the description usefully enumerates returned fields (brand, model, category, shop, price range, stock, variants, rating, source URL), which compensates well. Ten parameters are fully documented in the schema, so the only real gap is the absence of sibling routing guidance.

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 every one of the ten parameters is already documented, including defaults and the sort_by enumeration. The description adds no filtering, syntax, or interaction guidance beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ("Search products offered by shops on Vaper.club") and even enumerates the result fields, so the agent knows exactly what comes back. It does not, however, contrast itself with siblings like search_brands, search_shops, or compare_products, leaving that differentiation to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when users ask to find, identify or research vape products" gives a clear trigger context for invocation. There are no explicit exclusions or named alternatives, so an agent facing a brand- or shop-oriented query must decide on its own.

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