Skip to main content
Glama

Moqway

Search wholesale products

search_products
Read-onlyIdempotent

Search published products from verified Chinese factories. Use short English keywords (e.g. 'stainless steel hook', 'silicone baking mat'). Filters are optional. Returns cards with the lowest tier price, MOQ, handling time and the supplier's Moqway rating; better-rated suppliers rank slightly higher. Prices and MOQ are per sale unit: pieces_per_unit is 1 for products sold by the piece, otherwise the pack size (then from_price_per_piece is given too). Call get_product for SKUs, full price tiers and carton data.

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
limitNo
queryNoKeywords; omit to browse the newest listings
offsetNo
max_moqNo
categoryNo
certificationNoe.g. CE, FCC, RoHS, CPC, LFGB
ships_within_daysNoMax factory handling days before hand-over to the carrier
max_unit_price_usdNoOnly products whose lowest price per single piece is at or below this (products sold in packs are compared per piece)

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior the annotations cannot: result ranking ('better-rated suppliers rank slightly higher'), the exact card contents (lowest tier price, MOQ, handling time, rating), and how prices/MOQ are normalized per sale unit. Rate limits and total-result behavior are not mentioned, so not a 5.

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?

Front-loads what is searched, then query style, then result shape, then the pricing caveat, then the follow-up tool. Five sentences, each carrying distinct information with no repetition of schema content.

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?

No output schema exists, and the description compensates by describing the returned cards and the pricing normalization, which is the highest-risk ambiguity for this tool. What remains unstated is pagination/limit behavior and whether a total count is returned, minor gaps for an 8-param search tool.

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?

With only 50% schema description coverage, the description fills important gaps: query semantics (short English keywords, with examples), the optional nature of all filters, and the per-piece vs per-pack pricing semantics that govern max_unit_price_usd. Parameters like max_moq, certification and category are left to the schema, but those are largely self-explanatory or enum-backed.

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 and resource ('Search published products') plus a scoping qualifier ('from verified Chinese factories'). It is clearly distinguishable from the sibling get_product, which the description explicitly frames as the detail/SKU lookup rather than the search.

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 concrete query guidance ('Use short English keywords' with two examples) and states that 'Filters are optional', so an agent knows it can call with no args. It also routes to get_product for SKUs, price tiers and carton data. It stops short of explicit when-not-to-use conditions or a note on paging through results, keeping it below a 5.

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