Skip to main content
Glama

Rba

by io.github.pipeworx-io

Rba List Series

rba_list_series
Read-onlyIdempotent

Directory of the 71 RBA statistical tables and the series inside them — the discovery tool for rba_series. Pass query to search series NAMES/descriptions directly (e.g. "90-day bank bill rate", "3-year government bond yield") and get ranked series_id matches across tables in one call — this is what rba_series uses internally to resolve names, so a hit here is a hit there. Pass keyword to search table titles/categories instead (e.g. "housing loan", "cash rate", "inflation", "exchange rate") and see every series in the matched tables. Pass a table id directly to list all its series. Pass nothing to browse every table by category. NOT the same as list_tables (a different pack, Swedish population data) — this is rba_ prefixed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch series NAMES/descriptions directly (not just table titles), e.g. "90-day bank bill rate", "3-year government bond yield" — returns ranked (table, series_id) matches in one call.
tableNoOptional RBA table id to list every series inside it directly, e.g. "f6" (housing lending rates).
keywordNoOptional keyword to search table titles/categories and, for matched tables, their series names — e.g. "housing loan", "cash rate", "CPI", "exchange rate", "credit card".

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds meaningful behavior: keyword matching against table titles/categories, returning every series_id/name/units in one call, and the browse-by-category mode. No contradiction with annotations exists.

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?

The description is dense and front-loaded: purpose, usage patterns, and sibling-tool differentiation all appear without filler. Every sentence carries distinct information an agent needs.

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 discovery tool with two optional parameters and no output schema, this description is complete. It explains all invocation patterns, what the response covers, and how it relates to rba_series and list_tables.

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?

The input schema already provides 100% parameter description coverage with clear examples for both optional parameters. The tool description restates the main usage modes but adds little semantic detail beyond what the schema already 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?

The description states a specific resource and action: a directory of the 71 RBA statistical tables and the series inside them, positioned as the discovery tool for rba_series. It also distinguishes itself from list_tables, which is a different pack, so an agent can disambiguate it from sibling tools.

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?

Three explicit usage modes are given: pass a keyword, pass a table id, or pass neither to browse. It also names list_tables as a non-equivalent alternative, though it does not explicitly state when to use rba_series instead of this discovery tool.

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