Skip to main content
Glama
Sign In

Riksbank Se

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Cross Rates

cross_rates
Read-onlyIdempotent

Cross exchange rate between two SEK currency-fixing series over a date range. series1 is the base, series2 the quote; the result is series1/series2 per day. Example: series1 "SEKEURPMI", series2 "SEKUSDPMI" gives EUR/USD derived from the SEK fixings. Provide from (required) and optionally to (both YYYY-MM-DD); omit to to run through the latest date. Use SEK currency series IDs ending in "PMI" (see list_series).

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": {
      "from": "2026-01-01",
      "series1": "SEKEURPMI",
      "series2": "SEKUSDPMI"
    },
    "name": "cross_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRange end, YYYY-MM-DD (optional; defaults to latest).
fromYesRange start, YYYY-MM-DD, e.g. "2026-01-01".
series1YesBase currency series ID, e.g. "SEKEURPMI".
series2YesQuote currency series ID, e.g. "SEKUSDPMI".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "from": "2026-01-01",
+    "series1": "SEKEURPMI",
+    "series2": "SEKUSDPMI"
+  },
+  {
+    "from": "2025-06-01",
+    "series1": "SEKEURPMI",
+    "series2": "SEKUSDPMI",
+    "to": "2026-05-31"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true and destructiveHint as false. The description additionally discloses the mathematical operation (series1/series2 per day), the date range handling (omit to for latest), and the source of series IDs (SEK fixings ending in 'PMI'). No contradictions with annotations.

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 two sentences plus an example, front-loaded with the core purpose. Every sentence adds meaningful information without redundancy. The example is illustrative and reinforces the parameter semantics.

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 read-only computational tool with no output schema, the description adequately explains the return value (series1/series2 per day), covers all parameters (required and optional), and provides a concrete example. No additional context is needed for correct invocation.

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%, providing descriptions for all four parameters. The description adds value beyond the schema by explaining the relationship between series1 and series2 (base vs quote), the derived result formula, and the effect of omitting the to parameter. The example further clarifies parameter usage.

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 clearly states the tool computes cross exchange rates between two SEK currency-fixing series, specifying series1 as base and series2 as quote, with the result being series1/series2 per day. It includes a concrete example (EUR/USD derived from SEK fixings) and distinguishes itself from the sibling tool list_series by referencing it for finding series IDs.

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?

The description advises using SEK currency series IDs ending in 'PMI' and directs users to list_series for finding available series. It explains the optional to parameter and default behavior (run through latest date if omitted). However, it does not explicitly state when not to use this tool or mention alternatives beyond list_series.

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

All Riksbank Se 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