Skip to main content
Glama

Hnb Hr

by io.github.pipeworx-io

Hnb Currency Rate

hnb_currency_rate
Read-onlyIdempotent

HNB exchange rate for ONE foreign currency vs EUR (Croatia is in the eurozone). Pass the 3-letter ISO currency code (e.g. "USD", "GBP", "CHF"). Three modes: omit dates for the latest rate; pass date for a single historical date; pass start_date+end_date for a daily time series over that window. srednji_tecaj is the middle/reference rate. Rate values are strings with a COMMA decimal separator (e.g. "1,164900"). Dates are YYYY-MM-DD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSingle historical date, YYYY-MM-DD. Ignored if start_date is given.
currencyYes3-letter ISO currency code, e.g. "USD", "GBP", "CHF".
end_dateNoTime-series window end, YYYY-MM-DD. Required when start_date is given.
start_dateNoTime-series window start, YYYY-MM-DD.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations provide readOnly/idempotent hints. Description adds return format details (string with comma decimal separator), field name 'srednji_tecaj', and date format, which go beyond 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?

Single dense paragraph with clear structure: purpose, input format, three modes, data format. No wasted words.

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?

Given no output schema, description explains return structure and key field. Covers all usage modes. Lacks error handling but adequate for a simple rate query tool.

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%, baseline 3. Description adds examples, clarifies relationship between date and start_date/end_date, and explains modes, providing value beyond schema.

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?

Description clearly states tool fetches HNB exchange rate for ONE foreign currency vs EUR, with three modes (latest, single date, date range). Distinguishes from potential sibling 'hnb_exchange_rates' by emphasizing single currency.

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 describes three usage modes and date format. Does not explicitly exclude alternatives or provide when-not-to-use, but context is clear for agent decision-making.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical (beta is currently identical to ask_pipeworx), and deep_research and validate_claim also overlap with the ask_pipeworx family. The Polymarket tools are more distinct, but the query family creates real ambiguity.

Naming Consistency2/5

Tool names mix leading verbs (ask_, compare_, resolve_, scan_) with leading nouns (entity_profile, recent_changes, hnb_currency_rate) and there are multiple subfamily prefixes (ask_pipeworx_*, polymarket_*, hnb_*). All are snake_case, but no consistent verb_noun or noun pattern is followed.

Tool Count2/5

33 tools is well above the 25+ threshold, and the server name ('Hnb Hr') implies a narrow Croatian banking scope while the majority of tools are for a broad data research platform. Many meta-tools (discover_tools, suggest_questions, pipeworx_feedback, pipeworx_trending) inflate the count beyond what the apparent purpose needs.

Completeness3/5

The HNB currency functionality is complete (single and all rates, historical and latest), and the broader data platform offers good coverage via the ask_pipeworx router, subscriptions, and memory tools. However, there are gaps (no direct HNB news or historical archive tool, patents soft-fail, and out-of-domain tools like generate_llms_txt), and the mismatch between server name and content leaves the surface feeling incomplete.

Resources