Fromerica U.S. Trade Data

Find U.S. manufacturers on Fromerica

find_us_exporters

Read-only

Find U.S. manufacturers of a product. Returns (1) registered exporters: companies with a U.S. plant that Fromerica reviewed before publishing (Pro-plan companies are listed first and marked paid_placement=true), and (2) separately, unclaimed listings of U.S. manufacturers in the same industry built from public government records (not Fromerica members, not verified, not contactable through Fromerica). Always returns the link where the buyer can post a free request for quote (no account, 0% commission); Fromerica looks for matching U.S. manufacturers.

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_us_exporters"
  }
}

Input Schema

Name	Required	Description	Default
`product`	Yes	Product the buyer is looking for, e.g. "tractor parts".

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing ranking behavior (Pro-plan companies listed first, paid_placement=true), verification provenance (Fromerica reviewed before publishing), and that unclaimed public-record listings are not verified and not contactable. It does not cover result caps, pagination, or what happens with zero matches, though it does guarantee the RFQ link is always returned.

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?

Purpose is front-loaded in the first sentence, which is good, but the second sentence is a long compound construction with stacked parentheticals that is harder to parse than necessary. The RFQ-link sentence is valuable but reads as marketing copy ("0% commission") rather than operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly spends its space explaining the shape of the return (two result groups plus a guaranteed RFQ link) and the trust level of each group. Missing only edge-case behavior (empty results, result limits), which for a single-parameter read tool is a minor gap.

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?

Only one parameter and schema coverage is 100%, so the schema already carries the full meaning of `product`. The description adds nothing about format, specificity, or matching tolerance beyond restating "of a product".

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 ("Find U.S. manufacturers of a product") and immediately distinguishes the two result populations: verified registered exporters vs. unclaimed listings built from public records. No sibling (tariff/schedule/license tools) does manufacturer lookup, so the tool is unambiguously identifiable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicit usage is clear (a buyer searching for U.S. manufacturers of a given product), but the description never states when to prefer it over alternatives such as posting an RFQ directly, nor any exclusions or prerequisites. No sibling tool is named or contrasted.

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

All Fromerica U.S. Trade Data 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?