Skip to main content
Glama

StoragePrices: Australian Self-Storage Prices

fetch

Read-onlyIdempotent

Fetch the full self-storage pricing snapshot for a document id returned by 'search' — a published suburb page ('suburb:nsw:chatswood'), a facility suburb ('place:nsw:bondi-junction', answered as a 5 km radius snapshot around the centroid of the facilities recorded there — result_scope='nearby' when those facilities carry no current prices), a capital-city scope ('city:nsw:sydney', answered as the city-radius snapshot plus the city's Storage Box Index figure), or 'index:national' (the national Storage Box Index figure and the city-scope ids). metadata carries suburb, state, the scope's facility_count, unit_count, medians and observed_at, a dated citation_text, and typed_tool_args: pass these verbatim to any tool in metadata.typed_tool_args_for (a suburb or city document lists cheapest_storage / compare_prices / storage_near among others; a locality document lists price_distribution only) to continue on the same place and scope. typed_tool_args is null when the document is not a place. result_scope says what kind of document this is; the same string is still sent as coverage, deprecated: read result_scope. A row with no verified link has booking_handoff_url null and booking_handoff_reason: 'no operator URL on file' or 'operator URL host is not on the verified booking allow-list'. Link users with booking_handoff_url (tracked, live booking page); url is the StoragePrices page.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument id from a search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description stays consistent while adding substantial behavior beyond them: result_scope semantics including the 'nearby' fallback when facilities have no current prices, the deprecation of the `coverage` alias, typed_tool_args being null for non-place documents, and the two exact booking_handoff_reason values with null booking_handoff_url. That is exactly the extra context annotations cannot convey.

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?

The purpose is front-loaded in the first clause, but the body is a single dense run-on paragraph that packs document types, metadata fields, tool routing, a deprecation note and link semantics into one breath. Nearly every clause carries information, yet the lack of any structural break makes it hard to scan, and the trailing booking_handoff/url sentences read as return-field documentation that competes with the call-time content.

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 correctly takes on the burden of explaining the payload -- metadata contents, observed_at, citation_text, result_scope, and link fields -- which is thorough for a one-parameter fetch. It omits failure behavior (unknown, malformed or expired document ids), which is the main remaining gap.

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% and the single `id` parameter is already documented, so the baseline would be 3. The description earns a 4 by adding concrete id-format examples with prefixed namespaces and by tying the id back to search results, which meaningfully reduces the chance of the agent passing a raw suburb name.

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 opens with a specific verb and resource: 'Fetch the full self-storage pricing snapshot for a document id returned by search'. It immediately distinguishes itself from the sibling 'search' by stating that it consumes a document id, and it enumerates the accepted id forms ('suburb:nsw:chatswood', 'place:nsw:bondi-junction', 'city:nsw:sydney', 'index:national').

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?

It gives clear routing context: call this with an id from 'search', then pass metadata.typed_tool_args verbatim to tools listed in metadata.typed_tool_args_for (cheapest_storage, compare_prices, storage_near, or price_distribution for locality documents) to continue on the same place and scope. It does not explicitly state when not to call this (e.g. for cross-place comparisons), which keeps it short of a 5.

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