Sharpest price search

price_shopping_list

Read-only

Price a list of things to buy in one call. Each item is matched to the closest product sharpest.ai tracks (computer parts, electronics, collectibles, household staples), and you get the cheapest current US eBay asking price (item + shipping) for each, times its quantity, and the list total. Use it for a PC build, a homelab or NAS parts list, a set of cards, or a grocery/household list. Check the matched name: when it is not what was meant, refine that query and call again.

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": {
      "items": "<items>"
    },
    "name": "price_shopping_list"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	The shopping list: up to 30 objects, each {"query": what to buy, optional "quantity"}, e.g. [{"query": "2TB NVMe", "quantity": 2}]

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / items / description

Added value: +"The shopping list: up to 30 objects, each {\"query\": what to buy, optional \"quantity\"}, e.g. [{\"query\": \"2TB NVMe\", \"quantity\": 2}]"

AddedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, non-open-world), and the description adds real behavioral detail: matching against products sharpest.ai tracks, a category scope, and that the price is the cheapest current US eBay asking price including shipping. It also warns that matches can be wrong. Missing are edge behaviors such as unmatched items or empty results, and any rate/latency expectations.

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?

The core action and scope come first, followed by use cases and a recovery hint; every sentence carries information. The opening 'Price a list of things to buy' is slightly redundant with the name but is not wasteful.

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 no output schema, the description carries the burden of explaining results, and it does: per-item matched product, cheapest price including shipping, quantity multiplication, and list total. What is absent is what happens when an item cannot be matched or has no listing, which matters for a 30-item batch call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by explaining that each entry's price is multiplied by its quantity and summed into a list total. That clarifies the purpose of the optional quantity field rather than merely restating it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Price a list of things to buy in one call') and clarifies the batch scope, which implicitly sets it apart from single-item siblings like get_price. It stops short of naming any sibling explicitly, so an agent must infer the boundary rather than being told.

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 gives concrete use cases (PC build, homelab/NAS parts, cards, grocery list) and a recovery workflow: inspect the matched name and re-query if the match is wrong. It does not state when to prefer get_price or search_prices instead, so the alternative-selection guidance is incomplete.

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

All Sharpest price search 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?