SiteCheck Shop & Social

Ace Hardware product search: total hits and up to 30

ecommerce_ace_hardware

Read-only

Ace Hardware (US) product search: total hits and up to 30 products per page with product code, name, brand, price, MSRP, on-sale flag, UPC, manufacturer part number, product type, online stock, rating, review count, image and product link. From acehardware.com via a residential proxy. Takes about 30 s; allow a 60 s timeout. 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": {
      "query": "<query>"
    },
    "name": "ecommerce_ace_hardware"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Result page 1-20 (default 1)
`query`	Yes	Search words, e.g. cordless drill, paint roller

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only declare readOnly and openWorld, so the description carries real weight and delivers: it discloses the residential-proxy source, roughly 30 s latency with a 60 s timeout recommendation, a per-call price of $0.02 USDC via x402 on three chains, and that failed calls are not charged. Those are exactly the operational facts an agent needs before committing to a paid call.

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 and dense: the operation, cost, and latency all appear in the first two clauses. The one inefficiency is the long enumeration of returned fields (UPC, MPN, MSRP, rating, review count, etc.), which duplicates the output schema that already exists and could be trimmed without losing information.

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?

With an output schema present, the field list is a bonus rather than a necessity, and the description still covers the remaining unknowns: source site, proxy, latency expectation, timeout budget, and the paid-call model. An agent can decide and invoke correctly from this alone.

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 `query` and `page` are already documented in the schema, and a baseline of 3 applies. The description adds only the page-size context (up to 30 products per page), which helps the agent reason about pagination but does not extend either parameter's meaning.

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 (product search on Ace Hardware US) plus scope limits (up to 30 per page, total hits). The retailer is named explicitly, which is exactly how an agent picks this over the dozens of other ecommerce_* retailer siblings.

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?

Usage is implied by the retailer name: use this for acehardware.com products, not for Amazon, Target, or the other sibling stores. There is no explicit when-not-to-use clause, no guidance on when to prefer a sibling for cross-retailer price comparison, and no mention of query syntax limits or how the 30-per-page cap interacts with the 20-page maximum.

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

All SiteCheck Shop & Social 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?