Skip to main content
Glama

SNB cube dimensions

get_snb_cube_dimensions
Read-only

List an SNB data-portal cube's dimensions and item IDs so you can set precise get_snb_data dimension filters and fetch only the series you need.

Instructions

List the dimensions of any SNB data-portal cube and the item ids in each (e.g. devkum: D0 = monthly average 'M0' / end of month 'M1', D1 = currency 'EUR1', 'USD1', 'JPY100', …). Use the ids in get_snb_data's dimension_selection to fetch only the series you need. Examples: cube_id='devkum', cube_id='zimoma'.

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": {
      "cube_id": "<cube_id>"
    },
    "name": "get_snb_cube_dimensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
cube_idYesSNB cube id, e.g. 'devkum' (monthly FX), 'zimoma' (money market rates); see list_snb_datasets
languageNoLabel language: en or de (default en)en
max_items_per_dimensionNoMax items listed per dimension (default 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the example of what dimension items look like, but does not disclose truncation or pagination behavior tied to max_items_per_dimension, nor whether a cube id failure produces an error.

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 short sentences with the purpose front-loaded, followed by usage and examples; nothing is redundant. The enumerated item examples ('D1 = currency EUR1, USD1, JPY100, …') are somewhat verbose but demonstrate id formats that help the agent parse the output.

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 and three well-documented parameters, the description adequately conveys what is returned (dimensions plus their item ids) and how to consume it. It does not describe the response's overall structure or confirm whether listing is truncated at max_items_per_dimension, which is the main remaining gap.

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%, so cube_id, language and max_items_per_dimension are already documented in the schema, including the same 'devkum'/'zimoma' examples. The description adds no additional meaning about those parameters beyond what the schema states, so the baseline 3 applies.

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 opens with a specific verb and resource ('List the dimensions of any SNB data-portal cube and the item ids in each') and immediately shows the shape of the result via the devkum D0/D1 example. This makes it clearly distinct from get_snb_data, which fetches series rather than dimension inventories.

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?

It states the downstream use explicitly: 'Use the ids in get_snb_data's dimension_selection to fetch only the series you need', which tells the agent where this tool fits in the workflow. It gives no explicit when-not guidance and does not mention describe_data_cube or list_snb_datasets as alternatives for cube discovery.

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