Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

visible_promos

Read-onlyIdempotent

Currently visible public self-storage promotions/discounts for a market. Only advertised promo copy captured at observation time. Reversion price, duration, discount, and calculable 12-month cost are separate nullable fields and are never inferred from a bare intro price. 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.
providerNoProvider slug, e.g. 'national'.
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

A3.8/5.0
Behavior5/5

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

Annotations only cover safety/idempotency; the description adds substantial behavioural context on top: promo fields (reversion price, duration, discount, 12-month cost) are separate nullables and are never inferred from a bare intro price, and null booking links are explained by explicit reasons (no operator URL on file, host not on the verified booking allow-list). It also distinguishes `url` (the StoragePrices page) from booking_handoff_url (a tracked live booking page), which an agent could not learn from structured fields alone.

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 purpose is front-loaded, but the middle of the description drifts into agent-side rendering instructions ('include it as a Markdown link labelled ...', 'Render that result's commercial_disclosure immediately beside the action link'), which is presentation policy rather than tool semantics. These sentences are dense with useful content but interrupt the data-contract narrative and make the definition longer than its retrieval purpose requires.

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 and eight parameters, the description carries the return-value burden and does so partly: it names booking_handoff_url, booking_handoff_reason values, commercial_disclosure, and the `url` field, and it tells the agent to show introductory and ongoing prices. The full row shape (size, price fields, place) is not enumerated, so completeness is good but not exhaustive for a tool of this complexity.

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 eight parameters in detail, including the available_only and suburb-resolution semantics that the description partly repeats. The description adds little parameter meaning beyond what the schema states, leaving stay_months and move_in_date entirely to the schema, which is acceptable at baseline 3.

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 first sentence states a specific resource and scope: currently visible public self-storage promotions/discounts for a market, with the caveat that only advertised promo copy captured at observation time is included. It never names a sibling such as cheapest_storage or compare_prices, so the agent must infer differentiation, but the verb+resource is concrete enough to be actionable on its own.

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?

There is real conditional guidance for one parameter: default behaviour returns units storageprices.au shows a human, while available_only=false returns latest-known rows including delisted ones. The 'requires at least one of suburb, state, size_bracket, provider' constraint is simply restating the schema's anyOf, and the description gives no guidance on choosing this tool over the pricing siblings in the catalog.

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