SiteCheck Shop & Social

WebstaurantStore search results for restaurant

ecommerce_webstaurantstore

Read-only

WebstaurantStore search results for restaurant and foodservice supplies: item number, description, shown price per unit and product link, from the public results page (first page only). Related tools on this server, for a different need: ecommerce_rappi when you need Rappi restaurant menu and prices: for a Rappi store ID; ecommerce_aliexpress when you need AliExpress product search from the public search page. 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": "ecommerce_webstaurantstore"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words, 2 to 60 characters (letters, digits, spaces, dashes)
`limit`	No	How many items, 1 to 30 (default 10)

Output Schema

Name	Required	Description	Default
`q`	No
`count`	No
`items`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that only the first public results page is returned and spelling out the cost model: $0.002 USDC per successful call via x402 on Base, Solana or Arc, with failed calls free. Missing only rate/limit or auth details, and the output schema already covers the return shape.

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 returned fields are front-loaded in the first sentence, followed by alternatives and pricing. It is a bit dense with sibling routing detail and cost boilerplate, but every clause conveys actionable information for selection.

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 and 100% schema coverage, the description only needs to supply scope, cost and alternative routing, all of which are present. The single notable omission is how the capped first-page result set interacts with the limit parameter.

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%, with both q (2–60 chars, allowed characters) and limit (1–30, default 10) fully documented in the schema. The description adds no syntax or behavioral nuance beyond implying that results are capped to the first page, so the baseline 3 applies.

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+resource (search results for WebstaurantStore restaurant and foodservice supplies) and enumerates the returned fields (item number, description, price per unit, product link). This clearly distinguishes it from generic marketplace siblings such as ecommerce_aliexpress or ecommerce_rappi.

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?

Explicitly routes two adjacent needs elsewhere: ecommerce_rappi for Rappi menus/prices by store ID and ecommerce_aliexpress for AliExpress product search. It gives a clear selection context but never states a when-not-to-use condition for this tool itself (e.g., non-US suppliers or bulk/wholesale pricing).

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?