Skip to main content
Glama
Manufacturer and Supplier Finder MCP Server

Manufacturer and Supplier Finder MCP Server

Find manufacturers and suppliers

find_suppliers
Read-only

Search Google for manufacturers, wholesalers, or distributors by product and country, then verify each company site and return quoted evidence with confidence scores.

Instructions

Find manufacturers, wholesalers, and distributors for a product in one of 20 countries. Give product (for example cast iron cookware) and optionally country, role, and max_results. The actor searches Google, checks each company's own website with the Mamba Labs Website Phrase and Business Model Classifier, and returns one row per supplier: company_name, domain, website_url, roles_detected, product_evidence_text and role_evidence_text quoted from the site with their page URLs, and a 0.6 to 0.95 confidence. Directories, marketplaces, and social networks are never returned. When nothing qualifies, one free summary row says why. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per supplier returned plus the classifier's price per site checked.

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": {
      "product": "<product>"
    },
    "name": "find_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoSupplier type to search for and return. Default any.
countryNoTwo letter country code to search in. Default US.
productYesWhat the suppliers make or sell, for example cast iron cookware.
max_resultsNoMost supplier rows to return, 1 to 100. Default 20. About twice this many company sites are checked.
extra_keywordsNoUp to 5 extra search words, for example private label.
max_charge_usdNoOptional cap on the whole run, website checks included.
exclude_domainsNoCompany domains never to return.
require_product_mentionNotrue (default): return a company only when its own pages name the product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the internal pipeline (Google search plus the Mamba Labs Website Phrase and Business Model Classifier), the exact return shape, the 0.6-0.95 confidence band, the free summary row on empty results, error behavior with run ID, APIFY_TOKEN requirement, and the per-supplier plus per-site pricing model.

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?

Purpose is front-loaded in the first sentence and most sentences carry operational weight (exclusions, empty-result behavior, auth, billing). The enumeration of every return field in prose is somewhat dense for a single paragraph, but justified given there is no output schema.

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?

With no output schema, the description must carry return semantics, and it does so by listing the per-supplier fields, quoting conventions, confidence range, and the fallback summary row. It also covers auth, cost, and failure modes, so an agent has everything needed to call and interpret it.

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 schema already documents role, country, product, max_results, extra_keywords, max_charge_usd, exclude_domains, and require_product_mention. The description reinforces only a subset (product example, country/role/max_results) and adds a hint that about twice max_results sites are checked, which is already in the schema. Baseline 3 is appropriate.

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 set ('Find manufacturers, wholesalers, and distributors for a product') and constrains scope to one of 20 countries. An agent immediately knows what it produces and how it differs from a generic company-search tool. No siblings exist, so no differentiation is needed.

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 how to invoke it ('Give product ... and optionally country, role, and max_results') and defines implicit boundaries via the exclusion note that directories, marketplaces, and social networks are never returned. It lacks an explicit 'use this when / not when' statement, but with no sibling tools there is little to route against.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools