Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

price_distribution

Read-onlyIdempotent

Price distribution across facilities for a market + size bracket: per-facility median advertised prices plus known ongoing medians, coverage, and min/p25/median/p75/max summary. The coverage object separates a recognised locality from no known facilities, known but unpriced facilities, a thin sample, and sufficient distribution evidence. Promo-inclusive facility points are explicitly labelled. Requires at least one of: suburb, state, size_bracket.

Input Schema

NameRequiredDescriptionDefault
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.
size_bracketNoStorage unit size bracket.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: the coverage object distinguishes a recognised locality, no known facilities, known-but-unpriced facilities, a thin sample, and sufficient evidence, and promo-inclusive points are explicitly labelled. It does not discuss result-size limits or ordering, but the disclosure of how empty/thin results are represented is valuable.

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?

Two dense but well-organized sentences: the first front-loads what is returned, the second explains coverage states, with the input constraint last. No filler or repetition of the title. It is slightly packed with enumerated output fields, but every clause carries information.

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 usefully explains return contents and the meaning of the coverage field, which is the main interpretive risk for an agent. The place-resolution mechanics are mostly in the suburb parameter description. Given three simple parameters and no pagination, this is close to complete, with only minor gaps such as no explicit guidance on interpreting thin samples beyond being labelled.

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% and the schema already documents state, suburb (including matching, ambiguity, and capital-city radius behavior), and the size_bracket enum. The description's 'Requires at least one of' restates the schema's anyOf constraint rather than adding meaning. Baseline 3 applies since the schema does the heavy lifting.

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 opens with a specific verb-and-resource statement: distribution of price across facilities for a market plus size bracket, and enumerates the returned components (per-facility medians, known ongoing medians, coverage, min/p25/median/p75/max). It is unambiguous what the tool produces. It stops short of naming a sibling such as price_trends or best_value_storage to differentiate the distribution view from trend or ranking views.

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 only usage rule given is the input constraint 'Requires at least one of: suburb, state, size_bracket', which is a precondition rather than a when-to-use guide. Nothing tells the agent when a distribution query is preferable to price_trends, cheapest_storage, or operator_benchmark. Usage is implied by the tool's subject matter rather than stated.

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