Skip to main content
Glama

Get Cube

get_cube
Read-onlyIdempotent

Fetch a Swiss National Bank statistical data cube's time series as JSON. Cube discovery is limited, pick a cubeId from these documented, verified-live IDs: devkua = foreign exchange rates (CHF per currency); zimoma = money market & reference rates incl. SARON; rendoblid = Confederation/euro bond spot interest rates (yield curve); snbmonagg = monetary aggregates (M1/M2/M3, currency in circulation). Defaults to devkua (FX rates).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cubeId": "devkua"
    },
    "name": "get_cube"
  }
}

Input Schema

NameRequiredDescriptionDefault
cubeIdNoSNB cube ID, e.g. "devkua", "zimoma", "rendoblid", "snbmonagg". Default "devkua".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cubeId": "devkua"
      +  },
      +  {
      +    "cubeId": "zimoma"
      +  }
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds real value by disclosing the narrow valid-input domain (only four verified-live IDs) and the default cube, which implies failures for other IDs. It says nothing about response size, number of series returned, date-range control, or error behavior for an invalid cubeId.

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?

Front-loads the verb and resource, then immediately delivers the operational constraint and the ID catalog. No filler sentences, and the semicolon-delimited catalog is the densest possible encoding of the four mappings.

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?

Rich annotations plus 100% schema coverage mean the description need not re-document the single optional parameter, and it correctly spends its budget on valid value semantics. With no output schema, the brief note that the result is a JSON time series is the minimum needed; a hint at series granularity or date coverage would close the last gap.

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

Parameters4/5

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

Schema coverage is 100% and the parameter already carries examples and a default, setting a baseline of 3. The description earns above baseline by explaining what each ID actually retrieves (FX rates CHF per currency, SARON and reference rates, yield curve, M1/M2/M3 aggregates), turning opaque cube codes into selectable business concepts.

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?

States a specific verb and resource ('Fetch a Swiss National Bank statistical data cube's time series as JSON') and scopes it further by enumerating the four usable cube IDs with what each contains. It does not, however, distinguish itself from the sibling cube_structure tool, which plausibly covers cube discovery/structure, so an agent could still be unsure which to call for exploration.

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?

Gives clear operating context: cube discovery is limited, use only these verified-live IDs, and devkua is the default. What is missing is an exclusion or alternative — e.g. pointing to cube_structure when the desired cube is not in this list — so the agent has no stated fallback for the 'discovery is limited' problem the description itself raises.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.