Skip to main content
Glama

AgentPay

by io.github.yyxqqq777

Query China wholesale pricing

china_wholesale_pricing_query
Read-onlyIdempotent

Search factory-direct wholesale pricing samples for a product keyword (1688 / Yiwu style catalog). Returns items with MOQ, unit price USD, factory location, and supplier verification flags. Use for China sourcing research. Settles ~0.01 USDC via x402 per query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesProduct search query in English or Chinese, e.g. 'wireless earbuds' or '蓝牙耳机'.
max_priceNoOptional maximum target unit price in USD to filter results.
category_idNoOptional category filter ID when the user specifies a catalog category.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / category_id / description
      Added value: +"Optional category filter ID when the user specifies a catalog category."
    • addedInput schema / properties / keyword / description
      Added value: +"Product search query in English or Chinese, e.g. 'wireless earbuds' or '蓝牙耳机'."
    • addedInput schema / properties / max_price / description
      Added value: +"Optional maximum target unit price in USD to filter results."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses that the tool performs a search (read-only) and incurs a micro-transaction, which is transparent about its behavioral side effects. Annotations (readOnlyHint, idempotentHint) reinforce this, and there is no contradiction between the description and the annotations.

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?

The description is concise and well-structured, covering the core function, output summary, and cost in a few sentences. It is free of redundancy and directly addresses the tool's primary use case without unnecessary elaboration.

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?

The description adequately conveys the tool's output (item list with MOQ, price, location, verification) and mentions the cost, which is important for an agent to decide whether to invoke it. It does not detail error handling or pagination, but these are not essential for the core use case and the provided context (output schema exists) is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters have detailed descriptions: 'keyword' is explicitly defined with an example (English or Chinese), 'max_price' is described as an optional maximum unit price filter, and 'category_id' is explained as an optional catalog category filter. The schema coverage is 100% and the descriptions add meaningful context beyond the names.

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?

The description clearly states the tool's function: searching factory-direct wholesale pricing samples for a product keyword. It specifies the domain (1688/Yiwu style catalog) and the key output attributes (MOQ, unit price USD, factory location, supplier verification flags), leaving no ambiguity about its purpose.

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 description provides practical guidance by stating 'Use for China sourcing research' and mentions the cost of ~0.01 USDC per query. It does not explicitly contrast with sibling tools, but the distinct domain (China wholesale pricing vs payment status or xhs notes) makes the usage context clear enough.

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

All AgentPay toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct target: one checks payment configuration, one queries China wholesale prices, and two cover Xiaohongshu note detail vs. user notes. There is no meaningful overlap or risk of an agent confusing one tool for another.

Naming Consistency3/5

The names share a prefix-style convention and use snake_case, but the pattern after the prefix is inconsistent: 'agentpay_payment_status' and 'china_wholesale_pricing_query' are noun-oriented, while both xhs tools are get-prefixed. This is readable and predictable enough, but not a uniform verb_noun convention.

Tool Count5/5

Four tools is within the well-scoped range and each tool earns its place: payment preflight, wholesale sourcing, XHS note detail, and XHS user posts. The set is compact without feeling artificially padded or thin.

Completeness4/5

The server covers its apparent paid-data-access workflows well: agents can verify payment setup, then call the relevant paid lookup tools. Minor gaps exist—there is no XHS search tool, no wholesale supplier-detail endpoint, and no transaction/payment history—but they are workable gaps rather than dead ends.

Resources