Skip to main content
Glama

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, certification, 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.
    

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": "list_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoOptional. One filter field to list; omit it to list all five.

Output Schema

NameRequiredDescriptionDefault
fieldsNo
index_recordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / field / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "process",
      +      "material",
      +      "finish",
      +      "certification",
      +      "location"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / field / description
      Added value: +"Optional. One filter field to list; omit it to list all five."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is largely covered. The description still adds real behavioral context beyond them: `implies` expresses hierarchy such as aluminum-6061 implying aluminum, locations are truncated to words shared by at least three addresses, and `omitted_values` counts rarer terms that search_suppliers still matches despite not being listed here.

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 key purpose and the five fields are front-loaded in the first two sentences, with the per-value field semantics following. It is dense and every sentence carries information, though the paragraph is long enough that a reader must hold several details (implies, omitted_values, index_records, location threshold) at once.

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?

Despite a thin one-parameter schema, the description explains each returned element (key, label, records, implies, omitted_values, index_records) and the location truncation rule, which is exactly the nuance an agent needs to avoid misreading counts. With an output schema also present, nothing essential is missing.

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 100%, so the baseline is 3, but the description reinforces the single parameter's meaning by pairing 'pass `field` for one of them' with the enumerated valid values and the omit-to-list-all behavior. It adds useful downstream meaning (feed the label or key to search_suppliers) rather than just restating 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?

Opens with a specific verb and resource: 'List the values search_suppliers can filter on, with how many published suppliers declare each.' It also enumerates the five fields, so the agent knows exactly what surface this tool exposes and how it relates to search_suppliers rather than get_supplier.

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?

Clearly implies the discover-then-filter workflow by telling the agent to 'Pass a label or key as the matching optional argument of search_suppliers,' and states that omitting `field` lists all five. It never states when NOT to call this tool (e.g., when the agent already knows the valid keys), so it stops short of explicit exclusions.

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