Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Economics · RBA cash rate history

economics_cash_rate_series
Read-onlyIdempotent

The cash rate target over time, oldest first. decisions lists every change with its size in basis points; monthly gives one value per month, for charts and joins against other monthly series.

Price: 1¢ per call.

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": "economics_cash_rate_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of range (inclusive), same formats as `from`.
fromNoStart of range (inclusive): 2020-Q1, 2020-01, 2020-01-15 or 2020.
frequencyNo`decisions` — one row per change since 1990 — or `monthly` — the monthly average target since 1990.decisions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, non-destructive, closed-world read. The description adds genuinely new behavioral facts: results are ordered oldest first, decisions rows carry the change size in basis points, and each call costs 1¢ — cost disclosure is valuable context an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the subject and ordering stated first, mode semantics second, and the price isolated on its own line. Nothing is redundant or padded.

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 covers the two row shapes, ordering and cost, and all three optional parameters are documented in the schema. Minor gap: it does not say what happens when `from`/`to` are omitted, which an agent must guess.

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, and the description earns a bump by clarifying that `decisions` rows include the magnitude of each change in basis points while `monthly` yields one value per month — detail the schema's frequency description does not fully convey.

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 (the cash rate target) and a specific shape (a time series, oldest first), plus the two modes it can return. It implicitly separates itself from economics_cash_rate by being the historical series rather than the current rate, but it never names that sibling explicitly.

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 'for charts and joins against other monthly series' hints at when the monthly mode is appropriate, but there is no explicit when-to-use or when-not guidance, and no pointer to economics_cash_rate, economics_series or get_series_v1_economics_series as alternatives for other economic data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Microburbs Australian Property Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources