Skip to main content
Glama

search_suppliers

Read-onlyIdempotent

Use when the user asks which Chinese factories can make a part, which suppliers offer a process (CNC machining, injection molding, 3D printing, sheet metal, die casting, etc.), or wants suppliers filtered by region, certification or material. Returns only public L0 profile fields and canonical source URLs. Results are ranked by a public profile-completeness quality_score; no grid, price or payment fields are read.

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_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10.
regionNoProvince or city substring, e.g. Guangdong or Shenzhen.
processNoProcess/capability id to match primary profile or recent work.
materialNoMaterial substring, e.g. 6061 or titanium.
category_idNoCategory id, e.g. cnc-machining.
capability_idNoExact capability row id, e.g. cnc-machining/03.
certificationNoCertification name, issuer or number substring.
tolerance_max_mmNoOnly return suppliers whose declared tolerance is at or below this value in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the data exposure boundary — only public L0 profile fields plus canonical source URLs — and states that grid, price and payment fields are never read. It also reveals the ranking mechanism (profile-completeness quality_score), which is behavior the agent could not infer from annotations or schema.

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?

Three sentences, front-loaded with the "Use when..." trigger, followed by return scope and ranking. Dense and mostly waste-free, though the parenthetical process list is lengthy; a shorter clause could convey the same breadth.

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?

With eight all-optional params, no output schema, and annotations covering safety, the description is nearly complete: it explains result scope, ranking, and excluded data. It omits what happens on an unfiltered call (does it return everything up to limit?) and how id-based params interrelate, which is a minor gap.

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 coverage is 100% and every parameter already carries an example in its description, so the schema does the heavy lifting. The description's enumeration of process types (CNC machining, injection molding, 3D printing, sheet metal, die casting) adds marginal value as sample process values, but tolerance_max_mm and the id-based params are left to the schema.

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 states a specific verb and resource — searching Chinese factories/suppliers — and enumerates concrete query shapes (process such as CNC machining or injection molding, region, certification, material). This clearly distinguishes it from siblings like get_supplier (single entity) and search_works (different resource) without needing to open the schema.

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?

It gives explicit trigger conditions ("Use when the user asks which Chinese factories can make a part..."), which is strong when-to-use guidance. It does not name an alternative for drilling into a single supplier's full profile (get_supplier), though the note about returning only public L0 fields implies that boundary.

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