Skip to main content
Glama
Sign In

Hnb Hr

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hnb Exchange Rates

hnb_exchange_rates
Read-onlyIdempotent

HNB (Croatian National Bank) official exchange rates for ALL foreign currencies on a given date. Croatia is in the eurozone, so every rate is quoted AGAINST THE EURO (units of foreign currency per 1 EUR). Returns rows with valuta (3-letter ISO code), srednji_tecaj (middle/reference rate), kupovni_tecaj (buying), prodajni_tecaj (selling), datum_primjene (apply date). Omit date for the latest applicable rates. Rate values are strings with a COMMA decimal separator (e.g. "1,164900").

Input Schema

NameRequiredDescriptionDefault
dateNoApplicable date, YYYY-MM-DD, e.g. "2026-05-15". Omit for the latest applicable date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {},
+  {
+    "date": "2026-05-15"
+  }
+]
  2. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. Description adds meaningful context: rates quoted against EUR, return fields (valuta, rates, apply date), and comma decimal separator. No contradictions.

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?

Two sentences, front-loaded with purpose and key details. Every sentence earns its place: first introduces the tool, second details quotation and return format. No 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?

Given single optional parameter, no output schema, and full annotations, the description provides all necessary context: what the tool returns, how the data is expressed, and how to use the parameter. Complete for its complexity.

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% with clear schema description for the optional 'date' parameter. Description adds value by stating 'Omit for the latest applicable rates' and specifying the format 'YYYY-MM-DD' (already in schema but reinforced). Exceeds baseline 3.

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 'official exchange rates for ALL foreign currencies on a given date', differentiating from the sibling 'hnb_currency_rate' (likely for a single currency). It specifies the resource (HNB exchange rates) and the scope (all currencies, date-driven).

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 explains when to use: provides a date for a specific day or omit for latest rates. Implicitly contrasts with sibling tool 'hnb_currency_rate' which presumably handles single currencies. No ambiguity about usage context.

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

All Hnb Hr 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