Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

cheapest_storage

Read-onlyIdempotent

Cheapest observed advertised monthly self-storage prices for a suburb/state and/or size bracket. Optionally constrain by a max monthly price and/or unit floor area (sqm) — e.g. 'cheapest unit under $300 but more than 3 sqm in Fairfield, NSW'. Returns ranked facilities with prices and source URLs (chart-ready). Separately reports the lowest advertised price now and the lowest known ongoing price; intro rates with undisclosed reversion terms are labelled. Rows below the implausibly-cheap floor are excluded from the rows and the market population. A row is below it when its advertised rate is under $5, or when its ongoing rate (the advertised rate if none is known) is under $7 per square metre of unit area, capped at the per-size floor (locker $20, small $20, medium $30, large $50, extra_large $80, garage_plus $50, vehicle $30). A row with no recorded area is held to the per-size floor. Rows with no recorded size and only a category name (large warehouse, office, other, small warehouse, warehouse) are left out too: their prices are unreliable. Every row carries distance_km from the suburb centre, and the catchment object states the scope and the farthest result: the market is the suburb page's catchment, not a fixed radius, so a result can sit well outside the suburb. Reads available units by default — the same set storageprices.au shows a human; pass available_only=false for latest-known rows including units the source has stopped listing. For every unit with a non-null booking_handoff_url, include it as a Markdown link labelled ‘Check availability & book’ and preserve the URL exactly. Render that result's commercial_disclosure immediately beside the action link. Clearly show introductory and ongoing prices. When booking_handoff_url is null, use the provided ‘View facility’ action instead. Requires at least one of: suburb, state, size_bracket. A row with no verified link has booking_handoff_url null and booking_handoff_reason: 'no operator URL on file' or 'operator URL host is not on the verified booking allow-list'. Link users with booking_handoff_url (tracked, live booking page); url is the StoragePrices page.

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return. Anonymous callers are capped at 25-50 depending on the tool; a valid API key lifts the ceiling to 500. Values above your ceiling are clamped, not rejected.
stateNoState code, e.g. 'NSW', 'VIC', 'QLD'.
suburbNoAustralian suburb name, e.g. 'Chatswood'. A trailing state or postcode is peeled ('Sydney 2000'). Capital cities (Sydney, Melbourne, Brisbane, Perth, Adelaide, Canberra, Hobart, Darwin, Gold Coast) resolve to a city-wide radius scope. On price_distribution, an otherwise-empty exact Australian locality can resolve from the packaged ABS SAL snapshot even when StoragePrices has no prices there. Every answer states how the place resolved in `place`. `place.match_type` says how the name matched (exact, token or prefix, ...); when `place.ambiguous` is true the name also matches the places in `place.other_candidates` — confirm with the user or pass state.
max_area_m2NoOnly include units with at most this floor area in square metres. 0 means no area filter. An area bound excludes units whose area is unknown; filters_applied.dropped_unknown_area counts them.
min_area_m2NoOnly include units with at least this floor area in square metres. 0 means no area filter. An area bound excludes units whose area is unknown; filters_applied.dropped_unknown_area counts them. Must not exceed max_area_m2.
stay_monthsNoRequested stay in whole months (1-36). Used to calculate the rent component only when captured promotion duration and ongoing-price terms make that calculation reliable.
move_in_dateNoRequested move-in date (YYYY-MM-DD). Applied to captured promotion-date eligibility and echoed in the result. Future-date operator inventory filtering is unavailable and is identified in unsupported_filters.
size_bracketNoStorage unit size bracket.
available_onlyNoDefault true. True returns only units the provider still lists and a complete scrape has seen recently — the same set storageprices.au shows a human. Set false for every latest-known row, including units the source has stopped listing; those are historic observations, never an availability claim.
max_monthly_price_audNoOnly include units at or below this advertised monthly price (AUD). 0 means no price filter (echoed in filters_applied.ignored_zero_bounds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses substantial non-obvious behavior: implausibly-cheap exclusions with per-size floors, the per-square-metre rule, catchment scope that can exceed the suburb, distance_km on every row, and precise booking_handoff_url null semantics with reasons. It also explains that anonymous callers are capped and how intro rates with undisclosed reversion are labelled. This is unusually rich behavioral context that does not contradict the annotations.

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

Conciseness2/5

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

The purpose is front-loaded, but the body is a dense wall of parenthetical detail, including exact dollar floors per size category and a full list of excluded category names that an agent does not need to invoke the tool. Presentation instructions about Markdown link labels and placing commercial_disclosure beside the link further bloat the prose. Much of it does not earn its place in a tool description.

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?

There is no output schema, so the description carries the return contract, and it does: ranked facilities with prices, source URLs, chart-ready output, the catchment object, distance_km, booking_handoff_reason values, and how null links are represented. For a ten-parameter, filter-heavy search tool, the agent has enough to call it and interpret the result.

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 documents all ten parameters, setting a baseline of 3. The description adds meaning by showing how filters combine ('cheapest unit under $300 but more than 3 sqm in Fairfield, NSW') and by clarifying the intent of available_only and the price/area bounds, which goes modestly beyond the schema text.

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 opening sentence states a specific resource and scope: 'Cheapest observed advertised monthly self-storage prices for a suburb/state and/or size bracket.' That is a concrete verb-and-resource statement an agent can act on. It does not explicitly distinguish itself from siblings like best_value_storage or compare_prices, so it stops short of a 5.

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?

The description gives real conditional guidance for available_only (default true vs. false for latest-known rows) and states the at-least-one-of suburb/state/size_bracket requirement. However, it never names an alternative tool or says when to prefer best_value_storage, storage_near, or compare_prices instead, so selection guidance across siblings is left implicit.

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