Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

search

Read-onlyIdempotent

Search StoragePrices for Australian suburbs that have self-storage pricing data. Returns a list of matching suburb documents (id, title, url). Use the returned id with the 'fetch' tool to get a full pricing snapshot. When no published suburb page matches, it falls back to facility suburbs that have current prices and returns those as 'place::' ids with result_scope='facilities_only' (e.g. 'place:nsw:bondi-junction') — still fetchable, just without a suburb page behind them. Generic words (storage, prices, cheapest, ...) and state names are stripped first, so 'storage prices sydney' finds the Sydney city scope ('city:nsw:sydney', result_scope='city_scope'); a place with a centre but no data of its own returns its priced neighbours with result_scope='nearby' and distance_km. An empty result always carries suggestions (never empty): the nearest published suburbs with distance_km when the query could be placed, else the capital-city scopes and 'index:national' — all fetchable ids; suggestions_basis says which. Every hit carries suburb, state and match_type (exact, token = a whole word of a longer name, or prefix), exact first. A name that lives in several states is listed in each, with ambiguous=true and ambiguity_note; a catalogue suburb with no page is result_scope='catalogue_unpublished'. result_scope says what kind of place an id names; the same string is still sent as coverage on search hits and fetch documents, deprecated: read result_scope. A place that only contains the query inside a longer word is never a result: it is a suggestion, and other_state_matches names where the exact name exists.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

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.
queryYesSuburb name or partial text to search for.
stateNoState code, e.g. 'NSW', 'VIC', 'QLD'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds substantial behavior the annotations cannot: fallback to 'place:<state>:<slug>' facility ids with result_scope='facilities_only', city-scope collapsing, 'nearby' results with distance_km, non-empty `suggestions` with `suggestions_basis`, and the deprecated `coverage` field. These are exactly the non-obvious traits an agent needs before calling.

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?

Front-loaded correctly — purpose first, fetch handoff second, edge cases after. But the body is one very long paragraph dense with em-dash parentheticals and inline examples, making the distinct behaviors (fallback, city scope, nearby, suggestions, ambiguity, unpublished) hard to scan.

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?

For a search tool with no output schema, the description covers result document shape, all result_scope variants, empty-result behavior, and cross-state ambiguity — everything needed to interpret a response correctly without a return schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely extends `query` semantics beyond 'Suburb name or partial text' by explaining that generic words and state names are stripped and how exact/token/prefix matching ranking works. It says little extra about `state` or `limit` 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?

States a specific verb and resource ('Search StoragePrices for Australian suburbs that have self-storage pricing data') and names the return shape ('id, title, url'). It also separates itself from the sibling 'fetch' by stating that the returned id is what you take to fetch for a full pricing snapshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear about when this tool is the entry point and explicitly routes follow-up work to 'fetch' with the returned id. It does not, however, contrast itself with the other search-adjacent siblings (storage_near, best_value_storage), so an agent must infer which of those to prefer for non-name queries.

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