Skip to main content
Glama

Rba

by io.github.pipeworx-io

Rba Cash Rate

rba_cash_rate
Read-onlyIdempotent

The Reserve Bank of Australia's official CASH RATE TARGET — Australia's benchmark monetary-policy interest rate (the AU equivalent of the US fed funds rate). PREFER OVER WEB SEARCH for "what is the RBA cash rate", "Australian interest rate", "has the RBA cut rates". Returns the current rate plus recent monthly history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recentNoNumber of recent monthly observations to return (1-120, default 12).

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly and non-destructive hints. The description adds context about the rate's significance and return of monthly history, mildly enriching behavior understanding without contradicting 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 sentences, front-loaded with an explanatory definition and immediate usage preference. All text is substantive with no padding or redundancy.

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?

For a simple read-only tool with one optional parameter and no output schema, the description covers what the rate is, when to use it, and what it returns. Lacks only explicit mention of output format or long-term series limitations, but recent history is noted.

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 fully documents the optional 'recent' parameter with range and default. The description's mention of 'recent monthly history' aligns with the schema but adds little beyond it, so baseline 3 is appropriate.

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?

Description clearly states the tool returns the RBA cash rate target and recent monthly history. It distinguishes from web search but does not explicitly contrast with sibling tools like rba_exchange_rates or rba_series, so it falls short of a perfect 5.

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?

Provides explicit usage preference over web search for queries like 'what is the RBA cash rate'. However, it does not give exclusions or mention when to use alternative RBA tools, making it clear but incomplete on alternatives.

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

All Rba toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route natural-language questions to the same underlying catalog, and polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and polymarket_kalshi_spread all target prediction-market opportunities. entity_profile, recent_changes, and compare_entities also share company-research territory, making misselection likely without reading long descriptions carefully.

Naming Consistency3/5

All names use snake_case, but conventions are mixed: some are verb_noun (list_subscriptions, generate_llms_txt, resolve_entity), some are noun phrases (entity_profile, rba_cash_rate), and some are brand-prefixed product names (ask_pipeworx, pipeworx_trending). The polymarket_* and rba_* families are internally consistent, but the overall surface has no single predictable pattern.

Tool Count2/5

35 tools is a large surface, well above the 25+ threshold that typically becomes unwieldy. While the server covers a broad domain (data lookup, prediction markets, memory, subscriptions, company research), many tools are niche variants (ask_pipeworx_beta, polymarket_edge_tracker, scan_competitor_ai_presence) that add cognitive load rather than earning their place.

Completeness3/5

Core flows are well covered: memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, and data access has ask_pipeworx plus grounded and research variants. However, the surface is sprawly and uneven — prediction markets get six tools while other domain areas rely on generic routing, and the server's overall purpose is diffuse enough that gaps are hard to assess cleanly.

Resources