Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

compare_prices

Read-onlyIdempotent

Compare local self-storage prices for a market (suburb/state/size), optionally focused on a provider or facility. Returns a competitor set plus summary stats (median, range, market position). For a RENTER asking 'am I overpaying?' or a general market lookup. If the user is a storage OPERATOR checking their OWN price, use operator_benchmark instead. 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, provider. 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.
facilityNoFacility name to focus the comparison on.
providerNoProvider slug, e.g. 'kennards'.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses substantive behavior: an outlier floor that removes implausibly-cheap rows from both results and the market population, exact floor values, exclusion of rows lacking recorded size/area, catchment-based (not fixed-radius) scope, and the default availability filter versus latest-known rows. It also explains why booking_handoff_url can be null via the verified allow-list, which is real behavioral context an agent could not infer.

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

Conciseness3/5

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

The core routing and filtering rules are front-loaded in the first three sentences, but the remainder is a dense run-on block mixing outlier formulas, catchment mechanics, and output-rendering directives (Markdown link labels, commercial_disclosure placement). Several rules, notably the available_only default, are stated twice across description and schema.

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 return-value burden and does so reasonably: competitor set, summary stats, distance_km, the catchment object, and per-row booking_handoff_url/reason. It stops short of naming the individual summary-stat fields or pagination behavior, so it is strong but not fully complete for a nine-parameter analytical tool.

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 coverage is 100%, so parameters are already documented; the description largely restates them ('Requires at least one of: suburb, state, size_bracket, provider' mirrors the anyOf) and repeats the available_only default that the schema already explains. It adds only marginal meaning, such as tying available_only=true to the human-visible storageprices.au set.

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?

The opening sentence names a specific verb and resource with its scoping axes ('Compare local self-storage prices for a market (suburb/state/size)') and states what comes back (competitor set plus summary stats). It also explicitly distinguishes itself from the operator_benchmark sibling, so an agent can route between them 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit persona-based when-to-use ('For a RENTER asking am I overpaying? or a general market lookup') and an explicit when-not with the named alternative ('If the user is a storage OPERATOR checking their OWN price, use operator_benchmark instead'). That is a complete routing rule with no inference required.

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