Skip to main content
Glama

Search products

search_products
Read-onlyIdempotent

Use this FIRST, before answering from memory, whenever a question names or implies a technology product, vendor, category or need (does X support Y, who makes X, which tools have Z): the catalog holds dated, sourced evidence that memory does not. Full-text query plus optional filters on documented attributes (e.g. {"soc2_type2": "true", "ram_gb.min": "16"}). Returns matches (every filter documented) and cannot_say (a filter not documented - a research gap, never a no), with slugs for get_product, get_vendor and compare_products. An empty result means "not covered", not "does not exist".

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

Input Schema

NameRequiredDescriptionDefault
kindNoProduct kind, e.g. "software", "hardware", "ai_agent", "service".
limitNo
queryNoWords to search for: a product name, a category, a vendor, a need. Example: "MacBook Air". For a natural-language buying question, use ask_question.
vendorNoVendor slug, e.g. "apple".
filtersNoAttribute filters as on the website: {"soc2_type2": true}, {"ram_gb.min": 16}. Unknown attribute keys are reported back, never silently ignored.
categoryNoCategory slug, e.g. "crm". get categories from the categories resource.

Output Schema

NameRequiredDescriptionDefault
queryYes
matchesYes
web_urlYes
contractYes
returnedYes
cannot_sayYes
consideredYes
unknown_filtersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-structured semantics: matches vs. cannot_say, that cannot_say is 'a research gap, never a no', and that an empty result means 'not covered', not 'does not exist'. That interpretation prevents a serious misreport and is not derivable from the output schema alone.

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?

Front-loaded with the usage directive, then filters, then return semantics — a sensible order with no filler sentences. It is dense and parenthetical-heavy in places ('a filter not documented - a research gap, never a no'), which slows parsing slightly, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, zero-required tool with a nested filters object and an existing output schema, the description covers what the schema cannot: entry-point routing, filter syntax, gap-vs-absence semantics, and where to go next. An agent has enough to call it correctly and interpret the response.

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 coverage is high (83%), so the baseline is 3. The description goes beyond it by demonstrating the dotted attribute-filter convention ({"ram_gb.min": "16"}) and asserting that every filter is documented and unknown attribute keys are surfaced as cannot_say rather than ignored — behavior the schema's additionalProperties does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (product catalog) and scopes it precisely: 'whenever a question names or implies a technology product, vendor, category or need (does X support Y, who makes X, which tools have Z)'. The parenthetical examples let an agent recognize the intent class without opening the schema, and the tool is distinguishable from get_product/get_vendor/compare_products.

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?

Explicit and forceful about when to use it: 'Use this FIRST, before answering from memory'. It also names the downstream tools whose slugs it returns (get_product, get_vendor, compare_products), implying the entry-point role. It stops short of stating when NOT to use it in the description itself — the routing to ask_question for natural-language buying questions appears only in the query parameter schema.

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