Forever Works MCP servers
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| annual_averageA | BNR's annual average rate for a year, as ANAF converts foreign income in the D212 ("cursul de schimb mediu anual comunicat de BNR"): the mean of the twelve monthly averages, each the mean of the month's daily rates, to four places, with the monthly values and their day counts. Not the mean of the daily rates, which differs. A year not over yet answers the months so far with complete: false. |
| convertA | An amount converted to or from RON at BNR's reference rate, computed exactly and rounded once: to RON is amount x rate / multiplier, from RON amount x multiplier / rate. rate_rule picks the fixing: in_force (the day's, or the last banking day's before it, as rate answers) or last_before (the last one strictly before the day, the rule for an invoice in a foreign currency). Answers the result with the rate, its multiplier and the date BNR published it, so the conversion can be stated. One side must be RON; for two other currencies, convert twice. |
| healthA | Whether BNR's rates can be read now: the date of its latest fixing and how many currencies it carries. |
| rateA | The National Bank of Romania's reference rate in force on a day: RON per |
| ratesA | BNR's reference rates as series, the exact text BNR published. With date (default today): each currency's rate in force that day, from the day's fixing or the last banking day's before it. With from (and to, default today): every fixing BNR published in the window, oldest first, at most 366 days and 2000 rates a call. Without currencies, every currency BNR published. Each series carries its multiplier (RON per 1, or per 100 for HUF, JPY, KRW and a few others). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 5 tools
Each tool has a clearly articulated scope: health (availability), rate (single day), rates (series/window),annual_average (yearly figure), convert (arithmetic). The only real hazard is the rate vs rates pair, which differ solely by plurality and require reading descriptions to separate a point lookup from a series fetch.
All names are lowercase snake_case with no convention mixing, which is good. However the set blends nouns (rate, rates, health, annual_average) with a verb (convert), and rate/rates are distinguished only by a plural, a minor predictability gap.
Five tools is exactly right for a single-source exchange-rate server: point rate, series, annual aggregate, conversion, and a health probe. Nothing redundant and nothing padded.
The surface covers the full lifecycle of BNR data: current fixing, historical windows, yearly averages, arithmetic conversion, and availability checks, with explicit notes on limits and the two-step pattern for non-RON pairs. Gaps are minor, e.g. no currency roster/metadata tool and no direct cross-currency conversion, but both are workable via rates and convert.