Skip to main content
Glama

Mati Logistics — supplier sourcing

by com.matilogistics
OverviewDiscussionsAdmin

Discover suppliers

discover_suppliers
Read-only

Finds suppliers and manufacturers for a product or category and ranks them by fit with the request. Use it when someone needs suppliers for something, from a specific part to a broad category. It searches everything Mati Logistics holds (US customs records, supplier catalogues, industry directories and registers, company websites) and scores each candidate against the request. Returns the ranked list, often dozens of companies, each with a 0-100 fit score, a one-line reason, its role (manufacturer, packer_brand, distributor), country, shipment and catalogue counts, and the url of its page; plus how many companies were searched. Only search_for is needed: a sentence saying what kind of suppliers are wanted. phrases and hs_headings are optional search terms; when left out they are written from search_for, and the result shows the terms used under search_terms. Read-only, no side effects. Takes 10-20 seconds. Spends about one credit of a connected account; without an account, one free search a day per network address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phrasesNo6-16 short phrases (1-3 words) covering the request widely, as goods are written on a customs filing or a catalogue. Put the goods themselves first, exactly as the person means them ('taco shells'), then the closest variants, then the wider terms: for a category, its main products and the trade's terms ('soybean oil', 'tallow', 'shortening', 'olive oil' for oils and fats). Every word of a phrase must match, so keep them short; no country names.
countriesNoSupplier countries to require, full English names. Empty unless the person asked.
attributesNoUp to 3 things a buyer of these goods would compare suppliers on, as short column names in the person's language — whatever fits this request: for oils and fats, 'Oil types', 'Organic', 'Bulk or packaged'; for fasteners, 'Standards', 'Materials'. Each is filled per supplier from our records and shown as a column. Never the kind of company or its country: every row shows those already. Empty for none.
search_forYesWhat kind of suppliers are you looking for? A sentence: the goods, and any location, kind of company (maker or distributor), certification or other requirement. Results are ranked against it.
hs_headingsNoUp to 6 four-digit HS headings for the goods (1507 soybean oil, 1502 tallow). Empty if unsure.
company_typesNoOnly these kinds of company: manufacturer (makes it), packer_brand (packs or sells it under its brand), distributor (imports, trades, resells). Empty unless the person asked for a kind.
exclude_slugsNoSuppliers to leave out, by slug: for similar or alternative suppliers, the one they started from. Empty otherwise.
exclude_countriesNoSupplier countries to leave out. Empty unless the person asked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / request
      Removed value: -{
-  "description": "What the person wants, in a sentence, as the scoring brief: the goods, and any location, kind of company (maker or distributor), certification or other requirement they gave.",
-  "type": "string"
-}
    • addedInput schema / properties / search_for
      Added value: +{
+  "description": "What kind of suppliers are you looking for? A sentence: the goods, and any location, kind of company (maker or distributor), certification or other requirement. Results are ranked against it.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "request"
-]New value: +[
+  "search_for"
+]
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "request",
-  "phrases"
-]New value: +[
+  "request"
+]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses latency (10-20 seconds), cost (about one credit), a rate limit (one free search a day per network address without an account), and confirms no side effects. These are exactly the operational facts an agent needs before firing a slow, credit-spending search.

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 purpose and usage first, then behavioral and parameter detail. It is dense and the closing cost sentence is long, but nearly every clause carries information the agent would otherwise have to guess at.

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 carries the return contract fully — ranked list, 0-100 fit score, reason, role, country, shipment/catalogue counts, page url, plus the searched-company count. Latency, credit cost and the free-search fallback round out a complete picture for an 8-parameter search 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 100%, so the baseline is 3, but the description adds real meaning: only search_for is required, phrases/hs_headings are optional and auto-derived from search_for, and the derived terms come back under search_terms — an input/output linkage the schema does not express.

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 (finds), resource (suppliers/manufacturers for a product or category) and the differentiating behavior — ranking by fit with the request. This clearly separates it from retrieval siblings like get_supplier or get_coverage.

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?

"Use it when someone needs suppliers for something, from a specific part to a broad category" gives clear scope and spans narrow-to-broad requests. It stops short of explicitly excluding or routing to siblings (e.g. get_supplier for a known company), so it is context without exclusions.

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

All Mati Logistics — supplier sourcing toolsInspect
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