Skip to main content
Glama

Search products

search_products
Read-onlyIdempotent

Search wholesale products on B2B Market by keywords (any of ru/uz/en/zh). Returns title, price, seller and page URL. Optionally limit to a product category (see list_categories).

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
langNoAnswer language: ru (default), uz, en or ch (Chinese)
limitNoHow many results (default 10)
queryYesWhat to look for, e.g. "cement M400" or "pine lumber"
category_idNoProduct category id from list_categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered; the description adds value the annotations cannot by listing the response fields (title, price, seller, page URL) — important with no output schema. It says nothing about result caps or ranking/pagination behaviour beyond what the schema implies.

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?

Two tightly packed sentences: capability and return shape first, optional narrowing and the cross-reference second. No filler.

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?

For a four-parameter search tool with full schema coverage and no output schema, the description covers purpose, return fields and the category dependency adequately. The incomplete lang/zh-vs-ch signal and absence of any hint about result volume keep it from being complete.

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 coverage is 100%, so the four parameters are already documented; the description only reinforces that query accepts multiple scripts and that category_id comes from list_categories. It adds no detail for lang or limit, and its "zh" language code conflicts with the schema's "ch" enum value, which could confuse an agent.

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?

States a specific verb and resource ("Search wholesale products on B2B Market") plus the query domain (keywords in ru/uz/en/zh) and the returned fields. It is clearly distinguishable from get_product and search_services by resource, though it never explicitly contrasts itself with those siblings.

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?

Gives clear context for when to use it (keyword lookup, optional category narrowing) and routes the agent to list_categories for category ids. It stops short of stating exclusions, e.g. that exact-id lookups should go to get_product.

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