Skip to main content
Glama

List well-known SNB data cubes

list_snb_datasets
Read-only

Lists curated Swiss National Bank data-portal cube IDs with frequency and confidence flags, plus optional keyword filtering, to help select the right cube for dimension or data queries.

Instructions

Curated list of well-known Swiss National Bank data-portal cube ids (FX rates, money market rates incl. SARON, Confederation bond yields, SNB balance sheet, monetary aggregates, CPI, effective exchange rates) with frequency and a confidence flag for each id. Optional keyword filter, e.g. 'saron', 'bond yield', 'balance sheet', 'M3'. Then call get_snb_cube_dimensions or get_snb_data with the cube_id. Any other cube id from data.snb.ch also works with those tools.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keywords, e.g. 'saron', 'inflation', 'bond'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already supply readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine value beyond that by disclosing the return shape (frequency and a confidence flag per id) and by framing this as a curated static set rather than a live search. It does not explain what the confidence flag means, which is a remaining gap.

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

Conciseness4/5

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

Three sentences, front-loaded with the core purpose, then filter behavior, then the routing instruction. The parenthetical category list is long but earns its place by telling the agent what coverage to expect; nothing is redundant filler.

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?

No output schema exists, so the description correctly compensates by naming the returned fields (id, frequency, confidence flag) and the next-step tools. The only shortfall is the unexplained 'confidence flag' semantics, which an agent may need to interpret results.

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 coverage is 100% and the single 'query' parameter already carries a description with examples, so the baseline is 3. The description clarifies that filtering applies to the curated list and repeats example keywords ('saron', 'bond yield', 'M3'), adding modest value but no matching semantics beyond what the schema states.

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+resource ('Curated list of well-known SNB data-portal cube ids') and enumerates the covered domains (FX rates, SARON, bond yields, balance sheet, monetary aggregates, CPI, effective exchange rates). An agent can distinguish it from search_data_cubes or list_sources without opening a schema.

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?

Explicitly names the follow-up tools (get_snb_cube_dimensions, get_snb_data) and the handoff parameter (cube_id), plus the escape hatch that any data.snb.ch cube id works with those tools. It lacks an explicit 'use search_data_cubes instead when...' exclusion, so it falls short of full alternative routing.

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

Deploy Server

Other Tools