Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

inferred_market_rate

Read-onlyIdempotent

Inferred market ASKING-rate range ($/m²/yr) for self-storage by size band and location: a plain median of asking $/m²/yr from public advertised standard rates, promo-haircut 0.95 (floor). States radius_facility_count and nearest_priced_facility_km; when fewer than 8 comparable facilities sit inside the radius the headline falls back to the state pool and is flagged (fallback, headline_is_fallback, confidence='insufficient') — not a local rate. A market screen — not achieved rent, occupancy, or valuation.

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": {
      "lat": "<lat>",
      "lng": "<lng>",
      "size_bracket": "<size_bracket>"
    },
    "name": "inferred_market_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude of the location to query (required). Decimal degrees inside Australia, e.g. -33.796.
lngYesLongitude of the location to query (required). Decimal degrees inside Australia, e.g. 151.183.
radius_kmNoRadius to search for comparable facilities in kilometres (default 5). Must be greater than 0. A value below 1 is clamped to 1 and a value above 50 is clamped to 50, never rejected: radius_applied_km states the radius that ran and radius_note says when it was clamped.
size_bracketYesStorage unit size bracket (required). One of: locker, small, medium, large, extra_large, garage_plus, vehicle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Far exceeds the annotations (which only cover read-only/idempotent safety): it discloses the estimation methodology (plain median of advertised rates, promo haircut 0.95 as a floor) and the exact fallback threshold of fewer than 8 comparable facilities, naming the flags returned (fallback, headline_is_fallback, confidence='insufficient'). This is precisely the kind of result-interpretation context an agent needs before trusting the number.

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?

Front-loads the metric and unit before methodology, and each clause adds real information (method, fallback, exclusions). It is dense and parenthesis-heavy — flag names and thresholds are packed into one paragraph — but nothing is redundant.

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

Completeness5/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: it names key response fields (radius_facility_count, nearest_priced_facility_km, fallback, confidence) and explains the degraded-result case. For a read-only estimation tool this leaves no material gap an agent would need to call or interpret it correctly.

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 lat/lng bounds, radius clamping, and the size_bracket enum are already fully documented in structured fields. The description reinforces the 'comparable facilities inside the radius' concept but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific resource and metric: inferred market ASKING-rate range in $/m²/yr, keyed by size band and location, and clarifies it is a median of public advertised standard rates. It distinguishes itself from adjacent data concepts (achieved rent, occupancy, valuation) but never names a sibling tool such as price_distribution or market_overview, so routing is left partly to inference.

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 closing line 'A market screen — not achieved rent, occupancy, or valuation' implies usage context by exclusion, and the fallback note warns when the result is not truly local. However, there is no explicit when-to-use versus when-to-prefer a sibling like cheapest_storage or market_overview, so guidance is only implied.

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