Skip to main content
Glama

MRC Data — China's Apparel Supply Chain Infrastructure

Province Distribution

get_province_distribution
Read-onlyIdempotent

Show supplier distribution across Chinese provinces.

USE WHEN:

  • User asks "where are factories located" / "which provinces"

  • User needs to decide which region to source from

  • "where's [product] manufacturing concentrated in China"

  • "top provinces for [category]"

  • "geographic heatmap of suppliers for [product]"

  • "is sportswear mostly in Fujian or Zhejiang"

  • "which cities lead denim production"

  • "follow-up: 'break it down by province'"

  • "哪里有工厂 / 供应商分布 / 产业分布 / 地域分布"

  • "[品类] 主要在哪几个省 / 哪个省最集中"

WORKFLOW: Standalone discovery tool. get_province_distribution → search_suppliers (with top province) OR search_clusters (for clusters within that province) OR analyze_market (deeper view). RETURNS: { total_provinces, data: [{ province, supplier_count, top_cities: [{ city, count }] }] }

EXAMPLES: • User: "Where are most Chinese apparel factories located?" → get_province_distribution({}) • User: "Which provinces lead in sportswear manufacturing?" → get_province_distribution({ product_type: "sportswear" }) • User: "牛仔工厂主要分布在哪" → get_province_distribution({ product_type: "denim" })

ERRORS & SELF-CORRECTION: • Empty data for product_type → product_type keyword may not match. Try TYPO_MAP synonyms (tee→t-shirt, jeans→denim, 运动服→activewear) or drop the filter entirely. • Sparse results (< 3 provinces) → the product is niche. Try the parent category or broaden the term. • Rate limit 429 → wait 60 seconds; do not retry immediately.

AVOID: Do not call for cluster-level granularity — use search_clusters. Do not call without product_type if user is asking about a specific category — the unfiltered output is generic.

NOTE: Provinces are ranked by supplier count (Guangdong, Zhejiang, Jiangsu, Fujian typically lead). Source: MRC Data (meacheal.ai).

中文:按省份展示供应商分布,含每省 Top 城市。可按品类筛选。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_typeNoFilter by product type (e.g. sportswear, t-shirt, 运动服)
verbose_hintsNoIf true, response includes _interpretation annotations explaining what the data means and _guidance on how to use it

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description reinforces no destructive actions, adds error handling (429, empty data, sparse results), data ranking details, and data source, exceeding what annotations provide.

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?

Well-structured with clear sections (USE WHEN, WORKFLOW, RETURNS, EXAMPLES, ERRORS, AVOID, NOTE). Slightly long but every section adds unique value. Could be more concise but remains effective.

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?

Given no output schema, the description fully outlines return structure. Covers query patterns, error handling, workflow, multilingual examples, and data source. No gaps apparent for this tool's complexity.

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 100% and schema already documents both parameters. The description adds value through usage examples, synonyms for product_type, and error self-correction strategies, going beyond schema details.

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 explicitly states 'Show supplier distribution across Chinese provinces' and provides numerous specific use cases and query examples, clearly distinguishing it from siblings like search_clusters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Extensive 'USE WHEN' list with concrete query patterns, explicit 'AVOID' cases (cluster granularity, missing product_type), workflow integration, and alternative tool references. This provides comprehensive guidance.

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.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, covering different aspects of the supply chain: market analysis, supplier search, cluster comparison, fabric lookup, cost estimation, compliance checking, discrepancy detection, and alternatives. No overlapping tool boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., analyze_market, check_compliance, compare_clusters, search_suppliers). The pattern is uniform across all 20 tools, making it predictable for an agent.

Tool Count5/5

20 tools is well-suited for a comprehensive supply chain data platform. Each tool addresses a specific need without being excessive, and the count allows for deep coverage of the domain.

Completeness5/5

The tool surface covers the full lifecycle: market research, supplier discovery, fabric search, cluster info, cost estimation, compliance, credibility, discrepancy detection, and alternatives. No obvious gaps for the stated purpose.

Resources