SiteCheck Company Records

Clutch.co top B2B service providers in a category: name

b2b_clutch_reviews

Read-only

Clutch.co top B2B service providers in a category (web-developers, app-developers, agencies/seo, it-services...): name, rating and review count, verification badge, minimum project size, hourly rate, employee range, location, phone, service mix, sponsored flag and profile link; up to about 80 per page (pages 1-10). From clutch.co's public directory pages via a rendering residential proxy. Related tools on this server, for a different need: b2b_trustpilot_reviews when you need Trustpilot reviews for a company website: business name; b2b_seek_company_reviews when you need employer reviews from SEEK, the main job site of Australia. Price: $0.02 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": {
      "category": "<category>"
    },
    "name": "b2b_clutch_reviews"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Results page 1 to 10 (default 1)
`category`	Yes	Directory path as on clutch.co/<path>, e.g. web-developers, app-developers, agencies/seo, it-services

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses the data source and retrieval method (clutch.co public directory pages via a rendering residential proxy), the pagination ceiling (pages 1-10, ~80 per page), and the billing model ($0.02 USDC per successful call via x402; failed calls uncharged). That pricing and pagination context is precisely the kind of information annotations cannot carry.

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 is front-loaded and the category examples arrive before the field inventory. It is dense but mostly earns its length, though the enumerated field list partially duplicates the existing output schema and could be trimmed.

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?

Given an output schema and read-only annotations, the description supplies everything else an agent needs: category path format, pagination limits, source reliability caveats, and the cost per call. Nothing required to invoke it correctly is missing.

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 coverage is 100%, so both parameters are already documented in the schema, including the same category examples repeated in the description. The description's only addition is the page range bound 'pages 1-10', which is minor and partly duplicates the schema's '1 to 10' note. Baseline 3 is appropriate.

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 opens with a specific verb-and-resource statement ('Clutch.co top B2B service providers in a category'), gives concrete category paths, and enumerates the fields returned. It is clearly distinguishable from the many sibling directory tools because it names Clutch explicitly and describes the shape of the result.

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?

It explicitly routes two related needs elsewhere — b2b_trustpilot_reviews for Trustpilot reviews on a company website and b2b_seek_company_reviews for Australian employer reviews — which gives clear when-to-use-which guidance. What is missing is routing against the closest competitor directory, b2b_goodfirms_companies, and there is no statement of when not to use this tool.

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?