Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

best_value_storage

Read-onlyIdempotent

Best-value self-storage ranking using known ongoing rates: annualised price per square metre when area is known, then ongoing monthly price when area is unknown. Intro-only rows whose reversion price is undisclosed remain visible but receive no value rank. Transparent price ranking, not a personalised recommendation. 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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behaviour beyond them: the implausibly-cheap floor rules with per-size caps, exclusion of rows with only a category name and no area, the catchment scope that can place results well outside the suburb, and the meaning of booking_handoff_reason when no verified link exists. These are non-obvious data-quality and provenance facts an agent could not derive from the schema.

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 methodology and scope are front-loaded in the opening sentences, and the density reflects a genuinely complex ranking rule. It drifts toward output-rendering instructions (Markdown link labels, placing commercial_disclosure beside the action link) that lengthen the text, though with no output schema those instructions do earn some of their space.

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 10 parameters, no output schema and an open-world live-source dependency, the description carries the return-shape burden well: it explains distance_km, the catchment object, booking_handoff_url and booking_handoff_reason. Only the exact ranked-row fields and ordering beyond 'value rank' are left unstated.

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 the schema already documents all 10 parameters, and the description adds little per-parameter syntax. Its value comes from restating the anyOf requirement and the available_only semantics, which largely duplicate the schema; the baseline 3 is appropriate.

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 names a specific operation — a 'best-value self-storage ranking' computed from annualised price per square metre, falling back to ongoing monthly price — and states the value basis explicitly, so an agent knows this is a value-ranked list, not a raw price list or a distance search. It does not differentiate itself from close siblings such as cheapest_storage or compare_prices, leaving the agent to infer which ranking tool to pick.

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?

It gives concrete usage facts: at least one of suburb/state/size_bracket is required, available_only defaults to true and should be set false for latest-known rows, and intro-only rows without a reversion price stay visible but unranked. What is missing is comparison guidance — nothing says when to prefer this over cheapest_storage or storage_box_index, so the agent must guess between ranking siblings.

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