Microburbs Australian Property Data

Economics · Economic series history

economics_series_history

Read-onlyIdempotent

One series' observations (oldest first) with its metadata and the publisher's attribution. Optional from / to narrow the range; omit both for the full history (CPI goes back to 1948).

Price: 2¢ per call.

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": {
      "series_id": "<series_id>"
    },
    "name": "economics_series_history"
  }
}

Input Schema

Name	Required	Description
`to`	No	End of range (inclusive), same formats as `from`.
`from`	No	Start of range (inclusive): 2020-Q1, 2020-01, 2020-01-15 or 2020.
`series_id`	Yes	From /economics/series.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context, which it delivers: chronological ordering, inclusion of metadata and attribution, default-to-full-history behaviour, and the 2¢ per-call cost. It stops short of disclosing response size or any cap for very long histories like CPI back to 1948.

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?

Three tight sentences with the return shape front-loaded, the range rule second, and the cost last. No redundant restatement of the name or title, and every sentence carries information an agent needs.

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 usefully says what comes back (observations plus metadata and attribution) and how ranges behave. Gaps remain around failure modes for an invalid series_id and the practical size of a full-history response, which matter for a free-form string identifier with no enum.

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 schema already documents formats and inclusivity; the description adds the meaning the schema omits — that from/to are both optional and that omitting both returns the entire history. It also anchors series_id indirectly by pointing to /economics/series for valid values.

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 verb-less but precise outcome: one series' observations returned oldest-first, together with metadata and publisher attribution. It is clearly distinguishable from catalogue-style siblings such as economics_series or point-in-time siblings like economics_cpi_latest, though it doesn't name any of them 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?

Usage is implied: supply a series_id (obtained from /economics/series) and optionally narrow with from/to. The 'omit both for full history' rule is genuinely useful guidance, but there is no explicit when-to-use-this-vs-sibling statement and no warning about when a full-history pull is inappropriate.

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 tools Inspect

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

Need Help?