compare_clusters

shallow

ai.meacheal/mrc-data · Verify this server

Compare multiple Chinese apparel industrial clusters side-by-side on key metrics. PREREQUISITE: You MUST first call search_clusters to obtain valid cluster_ids. Do not guess IDs. USE WHEN user asks: - "compare Humen vs Shishi vs Jinjiang" - "which cluster has lower labor cost — Humen or Dongguan" - "side-by-side: Haining vs Xintang for denim" - "evaluate 3 clusters for my sportswear line" - "对比 [产业带1] 和 [产业带2]" / "哪个集群更适合 [品类]" - "rank these clusters by supplier count" - "which cluster has the highest scale for womenswear" - "follow-up: 'now compare the top 3 clusters you just listed'" Returns full records for each cluster so they can be compared on labor cost, rent, supplier count, scale, specializations, advantages, and risks. WORKFLOW: search_clusters → collect cluster_ids → compare_clusters → optionally get_cluster_suppliers on the winner to list factories in that specific cluster. RETURNS: { count: number, data: [full cluster objects with all fields] } EXAMPLES: • User: "Compare Humen, Shishi, and Jinjiang for sportswear sourcing" → compare_clusters({ cluster_ids: ["humen_women", "shishi_casual", "jinjiang_sportswear"] }) • User: "I want to evaluate Keqiao vs Zhili fabric markets" → compare_clusters({ cluster_ids: ["keqiao_fabric", "zhili_children"] }) • User: "对比虎门、石狮、晋江三个产业带" → compare_clusters({ cluster_ids: ["humen_women", "shishi_casual", "jinjiang_sportswear"] }) ERRORS & SELF-CORRECTION: • "Too many IDs (>10)" → split into batches of 10 and aggregate results in your response. • Fewer results than IDs sent → missing IDs were silently skipped (invalid cluster_id). Re-run search_clusters to verify IDs. • Empty data → all IDs were invalid. Re-run search_clusters and try again with fresh IDs. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not call with guessed cluster_ids — always resolve them via search_clusters first. Do not use to list factories in a cluster — use get_cluster_suppliers. Do not compare > 10 clusters in one call. CONSTRAINT: Max 10 cluster IDs per call. NOTE: Source: MRC Data (meacheal.ai). 中文:对比多个产业带的核心指标(最多 10 个)。

100.0/100

1 trials · measured 8 days ago

compare_clusters scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against ai.meacheal/mrc-data, measured 25 Aug 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-08-25100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: compare_clusters
[![Vouch score](https://vouch.tools/api/tools/d634094a-22a1-400c-87f9-24d8474ff231/badge.svg)](https://vouch.tools/tools/d634094a-22a1-400c-87f9-24d8474ff231)
compare_clusters — Vouch