CNC Compass

List CNC Compass search filters

list_facets

Read-onlyIdempotent

List the values search_suppliers can filter on, with how many published suppliers declare each.

    Fields are process, material, finish, and location; pass `field` for one of them. Each value has
    a stable `key`, a display `label`, a `records` count, and `implies` (broader keys a narrower one
    also matches, such as aluminum-6061 implying aluminum). Pass a label or key as the matching
    optional argument of search_suppliers. Locations are the city and province words that at least
    three supplier addresses share, most common first; `omitted_values` counts the rarer ones, which
    search_suppliers still matches. `index_records` is the number of published suppliers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`field`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No
`index_records`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark this readOnly/idempotent, so the description correctly focuses on behavior the annotations can't convey: locations are city/province words shared by at least three addresses, sorted most-common-first, with rarer values rolled into `omitted_values` (still matchable), and `index_records` as the published total. Only missing detail is whether `field` is required for a usable response.

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?

Front-loaded with the core purpose, then progressive detail on fields, keys, implies, and location semantics. Slightly dense with several distinct facts packed in, but every sentence carries information the agent needs.

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?

An output schema exists, so return shape needn't be restated, yet the description still explains the meaning of the returned fields (key, label, records, implies, omitted_values, index_records). Combined with the sibling cross-reference, an agent has everything needed to call and interpret this tool.

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 0% and the single `field` param has no description or enum, but the description compensates by enumerating the four legal values (process, material, finish, location) and stating its role in selecting a facet. That is meaning well beyond the bare `anyOf[string, null]` 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?

States a specific verb and resource — listing the filter values that search_suppliers accepts — plus the scope (published suppliers). It clearly separates itself from search_suppliers (which filters) and get_supplier (which fetches one record) without needing the schemas.

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?

Explains that the fields are process, material, finish, and location and that `field` selects one, then closes the loop by telling the agent to pass a returned label or key as the matching optional argument of search_suppliers. No explicit when-not or exclusion, but the workflow context is unambiguous.

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?