Skip to main content
Glama
Sign In

Rba

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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

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".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "keyword": "housing loan interest rates"
-  },
-  {
-    "table": "f6"
-  }
-]New value: +[
+  {
+    "query": "90-day bank bill rate"
+  },
+  {
+    "keyword": "housing loan interest rates"
+  },
+  {
+    "table": "f6"
+  }
+]
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Search 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.",
+  "type": "string"
+}
  2. Added

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds valuable behavioral context: it performs ranked matching, searches across tables in one call, and is the internal resolution mechanism for rba_series, which helps an agent predict result semantics.

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 front-loaded with the core purpose, then systematically walks through each parameter mode, and ends with a sibling disambiguation. Every sentence earns its place and there is no redundant filler.

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?

Despite having no output schema, the description gives sufficient shape of the results ('ranked series_id matches', 'every series in the matched tables') and covers all calling modes. For a read-only discovery tool with no required parameters, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description still adds real meaning beyond the schema: it contrasts query vs keyword behavior, provides concrete example searches, and clarifies that a table id lists all series directly. This goes well beyond the schema property descriptions.

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?

States a specific verb ('list', 'discovery tool') and resource ('71 RBA statistical tables and the series inside them'). It clearly distinguishes itself from list_tables by name and by domain ('Swedish population data'), so an agent can tell it apart immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly maps each parameter to its intended search mode: query for series names/descriptions, keyword for table titles/categories, table for direct table listing, and no arguments for browsing. It also names the sibling alternative (list_tables) and explains why it is not the same 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
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