Skip to main content
Glama

NBG currency list

nbg_list_currencies
Read-onlyIdempotent

Lists all currencies the National Bank of Georgia publishes a GEL rate for today, including names and quote units. Use it to check which codes have current rates before requesting conversions.

Instructions

Lists every currency NBG publishes a GEL rate for today, with its name and the unit quantity NBG quotes it in. NBG quoted other currencies in the past, so a code missing here may still have historical rates. nbgQuantity is the unit count NBG quotes the raw rate for (JPY is quoted as 1.6452 GEL per 100 JPY); for the rates themselves call nbg_get_rates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of currency names: en (default) or ka (Georgian). Codes, numbers and dates are identical in both.

Output Schema

NameRequiredDescriptionDefault
currenciesYes
effectiveDateYesCalendar date the returned rate took effect, as published by NBG

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely new context: the list is today-only and not exhaustive across time, and it defines what nbgQuantity means so a caller doesn't misread the returned numbers as rates.

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?

Three tight sentences, front-loaded with what the tool returns, then the historical-coverage caveat, then the nbgQuantity clarification and the sibling pointer. No sentence is redundant and nothing is buried.

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?

With an output schema present, return formatting need not be described, and annotations cover safety. The description still supplies the two things an agent could get wrong here — that the list is a today-only snapshot and that nbgQuantity is a divisor, not a rate — making it complete for this tool's complexity.

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 description coverage is 100% and the single enum parameter already documents en/ka and the guarantee that codes, numbers and dates are identical in both. The description adds no further meaning about the language parameter, so the baseline of 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?

Specific verb and resource with scope: 'Lists every currency NBG publishes a GEL rate for today, with its name and the unit quantity NBG quotes it in.' It also names the sibling that returns the actual rates, so the agent can distinguish it from nbg_get_rates without opening either schema.

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?

Explicit routing is given: 'for the rates themselves call nbg_get_rates.' It also warns that codes missing from this list may still have historical rates, which implies a history tool exists, though that sibling (nbg_rate_history) is never named, leaving the historical case one inference short of fully resolved.

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