SiteCheck Company Records

ImportYeti US import records: searches companies by name

b2b_importyeti

Read-only

ImportYeti US import records: searches companies by name and returns shipment counts, most recent shipment date, address and profile URL from ImportYeti's public search. Company search only, not individual bills of lading. Related tools on this server, for a different need: b2b_bbb when you need Better Business Bureau search: finds businesses by name; b2b_bizquest when you need businesses for sale on BizQuest: listing title, short. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "b2b_importyeti"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Company name to search, 2 to 80 characters

Output Schema

Name	Required	Description	Default
`count`	No
`query`	No
`source`	No
`results`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds substantial context beyond the readOnlyHint/openWorldHint annotations: exact price ($0.002 USDC per successful call), payment rails (x402 on Base, Solana or Arc), and the billing policy that failed calls are not charged. It also discloses the data source ('ImportYeti's public search') and output fields. It does not discuss rate limits or result-set size limits, so not a full 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?

Purpose and scope come first, followed by the disambiguation and then pricing — a sensible front-loaded order. It is a single dense paragraph that occasionally runs clauses together (the sibling-tool pitches plus payment details), but no sentence is wasted.

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 an output schema present, return values need not be explained, and the cost/billing model and scope boundary are covered. Minor gaps remain around data recency and whether searches are fuzzy, which matter for a single-parameter open-world lookup.

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?

The single parameter has 100% schema description coverage ('Company name to search, 2 to 80 characters'), so the schema already does the work. The description only restates 'by name' without adding matching behavior (fuzzy vs exact) or format hints, which is the baseline for full coverage.

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 — 'searches companies by name' against 'ImportYeti US import records' — and enumerates the returned fields (shipment counts, most recent shipment date, address, profile URL). It also draws an explicit boundary: 'Company search only, not individual bills of lading,' which separates it from bill-of-lading retrieval.

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?

Gives an explicit negative condition (not for individual bills of lading) plus named alternatives for adjacent needs: b2b_bbb for Better Business Bureau search and b2b_bizquest for businesses for sale. An agent can route between these without inspecting other schemas.

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

All SiteCheck Company Records 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?