Skip to main content
Glama

Search advertised wholesale prices

search_prices
Read-onlyIdempotent

Prices Australian sellers advertise on their own public pages, per kg, litre, dozen or each, excluding GST. Each result has the seller, the source link and the date it was read. Cheapest per-unit first. These are advertised prices, not a market rate: never average them. Example query: 'barramundi', 'lamb rack', 'sydney rock oysters'.

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": "search_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return. Default 25.
queryNoWhat to look for, e.g. 'rump steak'. Every word must match. Leave empty for everything current.
include_olderNoAlso return readings more than 30 days old, marked current:false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. On top of that the description discloses what annotations cannot: per-result fields (seller, source link, read date), sort order (cheapest per-unit first), unit normalisation and GST exclusion, which materially affects how results should be interpreted. It does not discuss result freshness beyond the read date or any rate limiting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what the data is, then result shape, then sort order, then the critical caveat, then examples. Five short declarative sentences with no filler; the caveat sentence is placed after the mechanics so it is not buried.

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 correctly takes on the job of describing returned fields and ordering, and the caveat about not averaging is essential for correct downstream use. Slight gap: nothing about dataset currency or refresh cadence beyond the per-result read date, which matters for a closed-world (openWorldHint=false) corpus.

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 all three parameters are already documented, including the 'every word must match' semantics and the 30-day/current:false behaviour of include_older. The description only adds illustrative query examples, which help but do not extend meaning beyond the schema — 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 and resource: advertised wholesale prices from Australian sellers' own public pages, with unit bases (kg, litre, dozen, each) and GST exclusion. The line 'these are advertised prices, not a market rate' implicitly draws a boundary against the market_rates sibling, so an agent can distinguish the two without opening either schema.

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?

Gives clear operating context ('never average them', advertised-vs-market-rate) and concrete example queries ('barramundi', 'lamb rack', 'sydney rock oysters') that show the intended granularity. It stops short of naming an alternative tool to use when an agent actually wants an averaged market figure, leaving that routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources