ForthClear Liquidation Marketplace

Search suppliers

search_suppliers

Read-only

Search the supplier directory. No sign-in required. Returns published company profiles only, including profiles a company has claimed. These are not lots for sale. A profile is compiled from public sources and is not an endorsement. Use search_inventory to find lots you can buy. Filter with query, country, type (3pl, returns_processor, brand_retailer, liquidator, other), or category.

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

Input Schema

Name	Required	Description
`q`	No	Alias for query.
`type`	No	Kind of company.
`limit`	No	Maximum profiles to return (default 20, max 50).
`query`	No	Words to match against the company name, city, or summary. `q` is accepted as an alias.
`country`	No	Country name or 2-letter code, matched exactly.
`category`	No	One category the profile lists, such as apparel or electronics.

Output Schema

Name	Required	Description	Default
`total`	Yes
`message`	Yes
`suppliers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedInput schema / properties / q

Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Words to match against the company name, city, or summary."New value: +"Words to match against the company name, city, or summary. `q` is accepted as an alias."

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's job is to add context — and it does: 'No sign-in required' covers auth, 'Returns published company profiles only' covers scope, and the note that profiles are compiled from public sources and are 'not an endorsement' flags data provenance. It stops short of describing pagination behavior or result ordering, which keeps it off a 5.

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 the core purpose, then progressively narrower disambiguation, with no filler sentences. The final filter sentence reads as a list appended to the end rather than integrated, a minor structural weakness.

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 annotations, a fully documented six-parameter schema, and an output schema that removes the need to explain return values, the description covers scope, auth, provenance and sibling routing. The absence of any hint about the default/maximum result count is the only notable 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?

Schema description coverage is 100%, so the schema already defines q, query, country, type, category and limit. The description restates the filter set and even repeats the type enum values already in the schema, but never mentions limit or the q alias — so it adds little meaning beyond the structured fields.

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 — 'Search the supplier directory' — and immediately distinguishes the result set ('published company profiles only, including profiles a company has claimed') from what a sibling returns ('These are not lots for sale'). An agent can separate this from search_inventory without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative explicitly and the condition that selects it: 'Use search_inventory to find lots you can buy.' Combined with the framing that this tool returns profiles rather than purchasable inventory, the routing decision is unambiguous.

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

All ForthClear Liquidation Marketplace 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?