Skip to main content
Glama

Get a CNC Compass supplier record

get_supplier
Read-onlyIdempotent

Return one published supplier record in full, by the slug from search_suppliers results.

    Includes identity (legal name, Chinese registered name when a registry lookup confirmed it, location, business type, founded year, employee range), the
    official website or source listing, the Made-in-China.com inquiry form when there is one,
    capabilities (processes, materials, certifications, equipment, industries, tolerance, maximum
    part size) and the facet keys search_suppliers matches, certificates, product families,
    facilities and news items with their own source pages, the listings the record was read from
    with permission basis and check date, and field-level evidence (the quote, page, extraction
    method, and review status behind each claim). `buyer_facts.checked` lists what CNC Compass confirmed (registry review,
    source factory, certificates on China's national register, a named third-party audit);
    `buyer_facts.profile` is what the supplier publishes about itself (tolerance, inspection, lead time,
    MOQ, Incoterms, payment terms, ...), each item with its quote and source page: present it as the
    supplier's statement, to be confirmed at quotation. `verification_status`, `factory_verification`
    ("Verified source factory" or empty) and `last_verified_at` report editorial review.
    An unknown slug is a tool error.
    

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": {
      "slug": "<slug>"
    },
    "name": "get_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe supplier's `slug` exactly as a search_suppliers result gives it, e.g. 'shenzhen-example-precision-co-ltd'.

Output Schema

NameRequiredDescriptionDefault
nameYes
newsNo
slugYes
facetsNo
sourcesNo
summaryNo
evidenceNo
locationNo
page_urlNo
productsNo
equipmentNo
materialsNo
processesNo
toleranceNo
facilitiesNo
industriesNo
legal_nameNo
buyer_factsNo
inquiry_urlNo
website_urlNo
certificatesNo
country_codeNo
founded_yearNo
website_kindNo
business_typeNo
certificationsNo
employee_rangeNo
last_verified_atNo
maximum_part_sizeNo
chinese_legal_nameNo
verification_statusNo
factory_verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"The supplier's `slug` exactly as a search_suppliers result gives it, e.g. 'shenzhen-example-precision-co-ltd'."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations (readOnly, idempotent, closed-world) by disclosing what the payload contains, how to interpret it, and where its limits are. The distinction between `buyer_facts.checked` (registry review, source factory, national-register certificates, named third-party audit) versus `buyer_facts.profile` (supplier self-published claims to be presented as statements, confirmed at quotation) is exactly the kind of interpretive context annotations cannot carry, and the error behavior for unknown slugs is stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense block that enumerates an extensive set of returned fields, much of which duplicates what the existing output schema already declares. The interpretive sentences (checked vs. profile, quote/evidence provenance, unknown-slug error) earn their place, but the long field inventory does not, and the lack of paragraph breaks makes it harder to scan than it needs to be.

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?

For a single-parameter, read-only lookup with an output schema, this supplies everything an agent needs: provenance of the input, error behavior, and critically the semantic framing of self-reported versus verified fields, which no structured field conveys. Nothing material 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?

The single parameter already has 100% schema description coverage with an example, which sets a baseline of 3. The description adds meaning beyond the schema by establishing where the slug comes from (a search_suppliers result) and that a mismatched value produces a tool error rather than an empty record.

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: 'Return one published supplier record in full, by the `slug`'. It also implicitly distinguishes itself from the list-oriented sibling by requiring a slug taken from search_suppliers results, so an agent can separate this from search_suppliers without opening either 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?

Gives clear context: use this after search_suppliers, passing the slug exactly as returned, and it explicitly states an unknown slug is a tool error, which is a useful precondition. It stops short of explicit when-not-to-use guidance or naming what to call instead when no slug is known (i.e. returning to search_suppliers), so it is clear but not fully routing.

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