Trade Intelligence

Get supplier profiles

get_suppliers

Read-only

Full profiles for up to 5 suppliers by ref (E1234): self-declared company type, founding year, location and street address (English and Chinese), certificates, staff, export markets, payment terms, listings with prices and MOQs, and on_record: government records about the supplier (FDA registration and 510(k) clearances, US recalls, import declarations naming it as maker), each with its source, date and link. Spends one search.

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": {
      "refs": "<refs>"
    },
    "name": "get_suppliers"
  }
}

Input Schema

Name	Required	Description	Default
`refs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower; the description still adds the meaningful cost signal ('Spends one search') and, absent an output schema, discloses the return payload including government records with source, date and link. It does not say what happens with invalid refs or partial results.

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?

A single front-loaded sentence that leads with what you get and the cap, then lists contents, then ends with the cost. The enumeration is long but every item earns its place by describing the return value.

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 and no annotation coverage of return data, the description carries that burden well by enumerating the profile sections. Remaining gaps are edge-case behavior (bad or unknown refs, partial success) rather than core invocation information.

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 0% and the schema only types refs as an array of strings; the description supplies the crucial ref format ('E1234') and confirms the 5-item cap in prose. That is real added meaning, though it does not explain how multiple refs are handled or whether order matters.

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 ('Full profiles for up to 5 suppliers by ref') and enumerates the returned data in enough detail (certificates, staff, export markets, payment terms, listings with MOQs, government records) that an agent can distinguish it from find_company or search_listings without opening a schema.

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?

The closing phrase 'Spends one search' signals cost and implies this is a deliberate lookup rather than a cheap browse, but the description never states when to prefer this over find_company or search_listings, nor any precondition for having refs in hand.

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?