Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

market_overview

Read-onlyIdempotent

National Australian self-storage market snapshot: per-size-bracket price quartiles (IQR) and a provider league table with median prices and facility counts. Chart-ready. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "market_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world, so the description need not restate safety. It adds meaningful behavioral context by defining the implausibly-cheap floor rules and the categories excluded from rows and market population, which directly affects interpretation of the output.

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 description is front-loaded with the main purpose and outputs before moving into exclusion rules. The floor-definition sentences are dense but earn their place because they explain important data-quality filtering; the category list is somewhat verbose but still relevant.

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 input parameters and no output schema, the description carries the burden of explaining outputs and does so adequately: quartiles, IQR, league table, median prices, facility counts, and chart-readiness. It also describes exclusions that materially affect results, though it could benefit from briefly clarifying currency or the precise league-table ranking metric.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline score is 4. The description appropriately does not spend wording on parameter meanings, and instead focuses on output and filtering behavior.

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 clearly states a specific resource and scope: a national Australian self-storage market snapshot with per-size-bracket price quartiles and a provider league table. It does not explicitly distinguish this tool from siblings such as price_distribution or operator_benchmark, so it falls short of the highest clarity score.

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 phrase 'market snapshot' implies the tool is for an overview rather than targeted filtering or comparison, but there is no explicit when-to-use guidance or named alternative. It does not explain when to choose this over sibling tools like price_distribution or operator_benchmark.

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