Skip to main content
Glama

Search CNC Compass suppliers

search_suppliers
Read-onlyIdempotent

Search published CNC Compass supplier records with a natural-language sourcing brief.

    Returns the normalized brief, the fields the brief did not state, matched suppliers with
    match reasons and source evidence, the filters applied with record counts, and paging
    fields (offset, limit, has_more). A brief with no recognisable process, material, finish,
    certification, or location returns no records and a follow-up question instead of the whole
    index. A stated certification (ISO 9001, IATF 16949, ISO 13485, AS9100, ISO 14001, ISO 45001,
    RoHS) returns only suppliers whose listing shows it. `query` is 3 to 5000 characters, `limit`
    1 to 20, `offset` 0 to 1000. When you already know the buyer's material, process, finish,
    certification, or location, pass them as the optional fields: each overrides the parsed value
    (for example material="aluminum 6061", process="CNC turning", finish="anodizing",
    certification="IATF 16949", location="Dongguan"); a value the index cannot match is ignored
    and listed in `retrieval.ignored_fields`.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of suppliers to return, 1 to 20. Default 5.
queryYesThe buyer's sourcing brief in plain language, 3 to 5000 characters: part, material, process, finish, tolerance, quantity, certification, location. Example: '500 anodized aluminum 6061 brackets, CNC milled, ISO 9001, near Shenzhen'.
finishNoSurface finish, e.g. 'anodizing', 'powder coating'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows.
offsetNoNumber of results to skip, 0 to 1000, for the next page when has_more is true.
processNoMachining process, e.g. 'CNC turning', '5-axis machining'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows.
locationNoChinese city or province, e.g. 'Dongguan', 'Zhejiang'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows.
materialNoMaterial, e.g. 'aluminum 6061', 'stainless steel 304'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows.
certificationNoRequired certification, e.g. 'ISO 9001', 'IATF 16949', 'ISO 13485', 'AS9100'; only suppliers whose listing shows it are returned. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows.

Output Schema

NameRequiredDescriptionDefault
briefYes
limitNo
answerYes
offsetNo
filtersNo
missingNo
has_moreNo
retrievalNo
suppliersNo
index_recordsNo
total_recordsNo
follow_up_questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / certification / description
      Added value: +"Required certification, e.g. 'ISO 9001', 'IATF 16949', 'ISO 13485', 'AS9100'; only suppliers whose listing shows it are returned. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows."
    • addedInput schema / properties / finish / description
      Added value: +"Surface finish, e.g. 'anodizing', 'powder coating'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows."
    • addedInput schema / properties / limit / description
      Added value: +"Number of suppliers to return, 1 to 20. Default 5."
    • addedInput schema / properties / location / description
      Added value: +"Chinese city or province, e.g. 'Dongguan', 'Zhejiang'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows."
    • addedInput schema / properties / material / description
      Added value: +"Material, e.g. 'aluminum 6061', 'stainless steel 304'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows."
    • addedInput schema / properties / offset / description
      Added value: +"Number of results to skip, 0 to 1000, for the next page when has_more is true."
    • addedInput schema / properties / process / description
      Added value: +"Machining process, e.g. 'CNC turning', '5-axis machining'. Optional. Overrides what the query says about this field; a value the index cannot match is ignored and listed in retrieval.ignored_fields. list_facets gives the values the index knows."
    • addedInput schema / properties / query / description
      Added value: +"The buyer's sourcing brief in plain language, 3 to 5000 characters: part, material, process, finish, tolerance, quantity, certification, location. Example: '500 anodized aluminum 6061 brackets, CNC milled, ISO 9001, near Shenzhen'."
  2. Changed2 schema fields changed
    • addedInput schema / properties / certification
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Certification"
      +}
    • addedOutput schema / $defs / SearchBrief / properties / certification
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Certification"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses the return payload shape, the empty-result fallback behavior, the exhaustive certification whitelist and its strict filtering semantics, and the ignored_fields mechanism for unmatchable values. These are the behavioral details an agent needs and that annotations cannot express.

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?

The core purpose and the empty-result rule lead, which is the right order, and the long parenthetical enumerations of certifications and example values are efficient packaging. Some content (numeric ranges, ignored_fields wording) duplicates the schema and could be trimmed without loss.

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?

For an 8-parameter search tool with an output schema, the definition covers the ambiguous parts: parsing vs. explicit overrides, certification strictness, and no-match behavior. The narrative about returned fields is partly redundant with the existing output schema, but nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3; the description mostly restates schema content (query 3-5000 characters, limit 1-20, offset 0-1000, override-and-ignore semantics). Its only genuine addition is a consolidated example of passing facet values together, which is marginal over the per-parameter schema text.

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 CNC Compass supplier records') plus the input modality ('a natural-language sourcing brief'), which immediately separates it from get_supplier (single-record lookup) and list_facets (vocabulary listing) even though those siblings are not named explicitly.

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 clear operational context: rely on free-text parsing when the brief is descriptive, but pass known material/process/finish/certification/location as optional fields so they override parsed values. It also explains the no-signal case (follow-up question instead of the whole index). It stops short of naming when to call get_supplier or list_facets instead.

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