Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

storage_box_index

Read-onlyIdempotent

The Storage Box Index for a suburb: estimated monthly rent for a standardised ~9 sqm unit and parity vs the national benchmark using known ongoing rates. The index is null when no local ongoing rate is observable; promo-inclusive monthly medians are not presented as annual costs. A suburb is indexed over its suburb-page catchment, the market cheapest_storage and compare_prices read, and over all of it: index_scope states the basis, facility_count, observation_count and population_capped. A capital city is answered as the public index page's city scope. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "suburb": "<suburb>"
    },
    "name": "storage_box_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoState code, e.g. 'NSW', 'VIC', 'QLD'.
suburbYesAustralian 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.
include_observationsNoDefault false: the index plus at most 25 observation rows and observations_total. True returns every observation row the index was computed from (up to the row cap).

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 already declare a read-only, open-world, idempotent, non-destructive operation, and the description adds substantial behavior beyond that: null handling, suburb-page and city scope, observation counts, population capping, and detailed exclusion rules for implausibly cheap rows. Those details materially affect how the returned index should be interpreted.

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 first sentence front-loads the purpose well, but the remainder is a dense run-on that mixes scope, null behavior, exclusion logic, and pricing floors. The long enumeration of per-size floors and category exclusions could be structured much more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex index tool with no output schema, the description covers inclusion criteria and scope well but does not fully explain the returned index fields or parity interpretation. It is adequate for selecting the tool, but an agent still has gaps about the response shape.

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 baseline is 3 and the schema already carries detailed semantics for `suburb`, `state`, and `include_observations`. The description adds context about catchment and city scope but does not add much parameter-level meaning beyond what the schema documents.

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 description states a specific resource and metric: the Storage Box Index for a suburb, covering estimated monthly rent for a standardised ~9 sqm unit and parity versus the national benchmark. It distinguishes this from the cheaper raw reads by naming `cheapest_storage` and `compare_prices` as market inputs rather than the index itself.

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 useful context about index scope, capital-city resolution, and when the index is null, but it does not explicitly state when an agent should call this instead of `cheapest_storage`, `compare_prices`, or `inferred_market_rate`. The guidance is implied by the tool's index purpose rather than framed as a clear selection rule.

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