Gemalli B2B Trade

Search products

search_products

Read-only

Search wholesale products published on Gemalli. Narrow by free text, category, manufacturer, country of origin, maximum minimum-order quantity, maximum price or delivery basis (Incoterms 2020 codes the seller confirmed). Returns product cards in the requested language with price range, minimum order and the supplier. Use it when the person is looking for goods to buy or source.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free-text search across name + description (FTS via migration 0016 with ILIKE fallback).
`limit`	No	Max results (1–50). Defaults to 12.
`locale`	No	Preferred locale for returned text.
`moqMax`	No	Max minimum-order-quantity threshold (inclusive).
`offset`	No	Pagination offset.
`country`	No	ISO 3166-1 alpha-2 country code (e.g. "UA").
`category`	No	Category slug filter (categories.slug).
`priceMax`	No	Max `price_from` threshold (inclusive).
`incoterms`	No	Delivery basis filter, Incoterms 2020 codes (e.g. ["FCA","DAP"]). A product matches when the seller confirmed ANY of the listed codes. Products without confirmed terms ("Incoterms on request") never match.
`manufacturer`	No	Manufacturer slug filter (manufacturers.slug).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

addedInput schema / properties / incoterms

Added value: +{
+  "description": "Delivery basis filter, Incoterms 2020 codes (e.g. [\"FCA\",\"DAP\"]). A product matches when the seller confirmed ANY of the listed codes. Products without confirmed terms (\"Incoterms on request\") never match.",
+  "items": {
+    "enum": [
+      "EXW",
+      "FCA",
+      "FAS",
+      "FOB",
+      "CFR",
+      "CIF",
+      "CPT",
+      "CIP",
+      "DAP",
+      "DPU",
+      "DDP"
+    ],
+    "type": "string"
+  },
+  "maxItems": 11,
+  "minItems": 1,
+  "type": "array"
+}

First observedSep 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No contradiction with annotations: readOnlyHint=true and destructiveHint=false align with the non-mutating 'Search' action. Beyond the annotations, the description adds behavioral context — results are localized product cards limited to seller-confirmed Incoterms and include price range, MOQ, and supplier. Pagination and limit behavior are left to the schema, which is a minor gap.

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?

Four sentences, each earning its place: scope, filter dimensions, return shape, and usage trigger. The purpose is front-loaded in the first sentence. The filter list partially overlaps with schema descriptions, but the description stays compact and free of 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 read-only search tool with all-optional parameters, full schema coverage, and no output schema, the description covers the essentials: what is searched, what filters exist, what results contain, and when to use it. Pagination defaults and locale mechanics are not mentioned, but those are already documented in the schema's parameter descriptions.

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 the schema fully documents all 10 optional parameters. The description's filter enumeration (free text, category, manufacturer, country, MOQ max, price max, Incoterms) summarizes the parameters but adds no meaning beyond what the schema already provides, meriting the baseline 3.

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 specific verb and resource ('Search wholesale products published on Gemalli') and states the output shape ('product cards in the requested language with price range, minimum order and the supplier'). It is clearly distinct from siblings like get_product, check_dual_use, or request_quote, though it never explicitly names the alternative.

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?

The final sentence gives explicit usage context: 'Use it when the person is looking for goods to buy or source.' This is clear when-to-use guidance, but there are no when-not-to-use conditions or named alternatives, so it does not reach a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gemalli B2B Trade tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?