highbrow_fame data APIs (pay per call)

Australian supermarket prices: Coles, Woolworths, ALDI, IGA, Harris Farm

grocery_au_search

Read-only

Live shelf prices from Australian supermarkets: Coles, Woolworths, ALDI, IGA and Harris Farm. Searches one store by keyword and returns products with price, was-price, unit price, special and multi-buy offers, pack size, brand and link; barcode, ingredients and nutrition where the store publishes them. Suited to grocery price comparison, cheapest-basket and weekly-specials questions for Australia. $0.01 per call, up to 50 products.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grocery_au_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum products (default 20).
`query`	No	Product search, e.g. "milk 2l".
`store`	No	coles, woolworths, aldi, iga or harris-farm. IGA and Harris Farm prices are set per store: choose the store with storeId or postcode (IGA) or location (Harris Farm).
`storeId`	No	IGA only: the IGA store number (for example 32600, Erskine Park NSW). Prices and specials differ per store. Wins over postcode. The answer names the store used in "store".
`location`	No	Harris Farm only: the store name or number whose prices to show, e.g. "Broadway", "West End", "Majura Park" or "37". Harris Farm sets prices per store. Default Broadway (37); the answer names the store used in "storeName" and in a note. Search needs "query" (a word to look for).
`postcode`	No	IGA only: a 4-digit Australian postcode. Uses the IGA store with that postcode, else the store with the nearest postcode in the same state. Ignored when storeId is given. Without storeId and postcode the default store is 32600 (Erskine Park NSW 2759) and a note says so.
`searchUrl`	No	Instead of query: a category, specials or product link of the store (not for iga or harris-farm).
`onlySpecials`	No	Only products on special (skipped products are not returned).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations it discloses cost ($0.01 per call), a result ceiling (up to 50 products), the one-store-per-call constraint, and the non-obvious per-store pricing behavior with concrete defaults (IGA 32600 Erskine Park, Harris Farm Broadway 37) and the fact that a note reports which store was used. That is exactly the kind of context 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?

Three front-loaded sentences with no filler: scope, then return payload, then fit and cost. The trailing '$0.01 per call, up to 50 products' fragment is efficient but slightly tacked on; otherwise the prose is dense and purposeful.

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 an 8-parameter, no-output-schema tool this is complete: it enumerates what comes back (price, was-price, unit price, specials, multi-buy, pack size, brand, link, barcode, ingredients, nutrition) and warns that some fields are conditional on what the store publishes, so an agent knows what to expect from a 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 the schema already explains limit, query, store, storeId, postcode, location, searchUrl and onlySpecials in detail. The description reinforces the key semantic — that query and searchUrl are alternatives and that store selection changes which prices come back — but adds little syntax or format detail beyond the schema, so it sits slightly above the baseline rather than far above it.

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 ('searches one store by keyword', 'live shelf prices') plus the exact store set and the returned fields. The 'Australian supermarkets' scope cleanly separates it from grocery_nz_search and grocery_uk_search without needing to name them.

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?

Names the question types it suits (price comparison, cheapest-basket, weekly specials) and implicitly rules out cross-store comparison by stating it 'searches one store'. It never states when to prefer a different tool or what to do if the requested store is unsupported, so it stops short of full when/when-not guidance.

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

All highbrow_fame data APIs (pay per call) 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?