CNC Compass

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`.

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`finish`	No
`offset`	No
`process`	No
`location`	No
`material`	No
`certification`	No

Output Schema

Name	Required	Description	Default
`brief`	Yes
`limit`	No
`answer`	Yes
`offset`	No
`filters`	No
`missing`	No
`has_more`	No
`retrieval`	No
`suppliers`	No
`index_records`	No
`total_records`	No
`follow_up_question`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

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

First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, closed-world, idempotent behavior, and the description adds substantial context beyond that: returned fields, no-match follow-up behavior, certification filtering, optional-field override semantics, and ignored_fields reporting.

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 definition is front-loaded and dense, with no obvious waste. Some return-field detail overlaps the output schema, but most of it adds behavioral meaning, so the length is largely justified.

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 the tool's complexity, the zero schema-description coverage, and the presence of annotations and an output schema, the description is complete enough for an agent to invoke the tool correctly. It covers input ranges, optional-field semantics, result behavior, and no-match handling.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: it documents query length, limit and offset ranges, optional material/process/finish/certification/location fields, override behavior, examples, and ignored_fields handling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 published CNC Compass supplier records using a natural-language sourcing brief. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like get_supplier or list_facets.

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 clear usage context: use a natural-language brief, and pass known material/process/finish/certification/location fields when available. It also explains the no-match behavior. However, it does not explicitly say when to use 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.

All CNC Compass tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?