Trade Intelligence

Find a company by name or website

find_company

Read-only

Find a company the buyer names, by its English or Chinese name or its website (e.g. 'Bangli Medical', '浙江邦立医药用品有限公司', 'ykbangli.com'). Searches the Chinese suppliers here and companies known only from government records (refs F…, FDA-registered sites with no supplier profile; refs C…, makers named on Chile's 2025 import declarations). Returns each match's name, what it matched on, its self-declared type and profile for suppliers, and on_record: government records with source links. No match is not evidence against a company. Spends one search.

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

Input Schema

Name	Required	Description	Default
`name`	No	The company name as the buyer gave it, English or Chinese, or a website
`website`	No	The company's website or email domain, if given

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint false), the description discloses the cost model ('Spends one search'), the meaning of negative results, the two government-record namespaces and their origins (FDA-registered sites, Chile 2025 import declarations), and the on_record/source-link behavior. These are business facts an agent cannot derive from structured fields.

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

Conciseness5/5

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

Three sentences, front-loaded with the lookup key and examples, followed by coverage and return shape, ending with the negative-result caveat and cost. No filler; every clause carries operational information.

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 supplies the return shape (name, matched field, self-declared type/profile, on_record with source links) and the search cost. For a two-parameter read-only lookup, nothing an agent needs to call it correctly 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 baseline is 3, but the description adds concrete format examples (English and Chinese company names, a bare domain) and clarifies that a website may be supplied as the name, which meaningfully reduces ambiguity about which field to populate.

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?

The description states a specific verb and resource ('Find a company') along with the exact matching keys (English name, Chinese name, or website) and the corpora searched (Chinese suppliers plus government-record refs F… and C…). An agent can tell this apart from discovery tools like search_listings or get_suppliers without opening any 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?

The description makes the intended use clear ('a company the buyer names') and explains what negative results mean ('No match is not evidence against a company'), which is real guidance. It does not explicitly name alternatives it should not be used for (e.g. discovering unknown suppliers), so the when-not side is left to inference.

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

All Trade Intelligence 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?