SiteCheck Company Records

Manta US small-business directory search by keyword

b2b_manta

Read-only

Manta US small-business directory search by keyword and city/state: business id, name, street, city and state, phone, website, claimed flag, description and Manta profile link, about 10 per page. From manta.com via a residential proxy. Related tools on this server, for a different need: b2b_bbb when you need Better Business Bureau search: finds businesses by name; b2b_doximity when you need US clinician data from Doximity's public directory. Price: $0.01 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": {
      "query": "<query>",
      "city": "<city>",
      "state": "<state>"
    },
    "name": "b2b_manta"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	US city, e.g. Austin
`page`	No	Result page 1-10 (default 1)
`query`	Yes	Business type or name, e.g. plumber, dentist, Acme Corp
`state`	Yes	Two-letter US state, e.g. TX

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/openWorldHint, it discloses genuinely useful behavior: results are paginated at about 10 per page, data is scraped through a residential proxy, the call costs $0.01 USDC via x402 across Base/Solana/Arc, and failed calls are not charged. The billing and failure policy in particular is context an agent cannot obtain from the annotations at all.

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 operation and return fields, then pricing last, which is the right priority order and contains no filler sentences. The sibling-routing clause is comparatively long given how many siblings exist, though it is still scoped to two named tools rather than a list.

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?

For a 4-parameter read-only lookup with an output schema, the description covers source, scope, page size, cost model and alternatives — everything an agent needs before calling. Return-value details are correctly delegated to the output schema, and nothing material 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 description coverage is 100%, so query/city/state/page are already documented in the schema, giving a baseline of 3. The description's only added parameter semantics is the approximate page size ('about 10 per page'), which loosely informs the page parameter but adds no format or range detail beyond the schema's 'Result page 1-10'.

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 gives a specific verb+resource pair (Manta US small-business directory search by keyword and city/state) and enumerates exactly what comes back: business id, name, street, city/state, phone, website, claimed flag, description, Manta profile link, ~10 per page. It also names the source (manta.com via residential proxy), which distinguishes it from generic business-search siblings.

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 the agent elsewhere by naming b2b_bbb for Better Business Bureau lookups and b2b_doximity for US clinician data, each with the condition that selects it. It stops short of stating when to prefer this tool over the other closest directory siblings (e.g. b2b_yellowpages, b2b_angies_list), so exclusion guidance is partial rather than complete.

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?