Skip to main content
Glama
Sign In

fxapi Exchange Rates MCP Server

by com.fxapi.api
OverviewDiscussionsAdmin

Latest exchange rates

getLatest

Returns the latest exchange rates for a given base currency (default USD). The update interval of the returned data depends on your subscription plan (from daily down to minutely).

Optional representations, none of which changes the default response: shape=compact for plain values ("EUR": 0.918456), precision to round, inverse=true for the value of one unit of each currency in the base currency, include=change for the change since the previous day's close, and format=csv.

Input Schema

NameRequiredDescriptionDefault
typeNoFilter the returned currencies by type.
shapeNo`default`: every rate as `{"code": "EUR", "value": 0.918456}`. `compact`: plain values, `"EUR": 0.918456`.
formatNo`json` (default), `csv` or `xlsx`. CSV has a header line and one row per currency (and point in time), values without exponent notation. `xlsx` is the same table as an Excel workbook (one sheet, bold frozen header row, numbers as numbers), sent as a download named after the endpoint, e.g. `latest.xlsx`.
includeNo`change` adds `change` and `change_pct` to every rate: the difference to the close of the day before `last_updated_at` (`meta.change_since`), computed like `/v1/fluctuation`. Null when that close has no rate for the currency. Not with `shape=compact`.
inverseNo`true` adds `inverse` to every rate: the value of one unit of the currency in the base currency (1 / value). Not with `shape=compact`.
precisionNoRound every value to this many decimals (0 to 10). By default values carry up to 10 decimals (10 significant digits below 0.1).
currenciesNoComma-separated list of currency codes to include (e.g. `EUR,USD,CAD`). The array form `currencies[]=EUR&currencies[]=USD` is also accepted. By default all supported currencies are returned.
base_currencyNoThe base currency that all returned values are relative to. Defaults to `USD`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / precision / description
      Previous value: -"Round every value to this many decimals (0 to 10). By default values carry up to 10 decimals."New value: +"Round every value to this many decimals (0 to 10). By default values carry up to 10 decimals (10 significant digits below 0.1)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"`json` (default) or `csv`. CSV has a header line and one row per currency (and point in time), values without exponent notation."New value: +"`json` (default), `csv` or `xlsx`. CSV has a header line and one row per currency (and point in time), values without exponent notation. `xlsx` is the same table as an Excel workbook (one sheet, bold frozen header row, numbers as numbers), sent as a download named after the endpoint, e.g. `latest.xlsx`."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "json",
-  "csv"
-]New value: +[
+  "json",
+  "csv",
+  "xlsx"
+]
  3. Changed5 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
+  "description": "`json` (default) or `csv`. CSV has a header line and one row per currency (and point in time), values without exponent notation.",
+  "enum": [
+    "json",
+    "csv"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / include
      Added value: +{
+  "description": "`change` adds `change` and `change_pct` to every rate: the difference to the close of the day before `last_updated_at` (`meta.change_since`), computed like `/v1/fluctuation`. Null when that close has no rate for the currency. Not with `shape=compact`.",
+  "enum": [
+    "change"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / inverse
      Added value: +{
+  "description": "`true` adds `inverse` to every rate: the value of one unit of the currency in the base currency (1 / value). Not with `shape=compact`.",
+  "type": "boolean"
+}
    • addedInput schema / properties / precision
      Added value: +{
+  "description": "Round every value to this many decimals (0 to 10). By default values carry up to 10 decimals.",
+  "type": "integer"
+}
    • addedInput schema / properties / shape
      Added value: +{
+  "description": "`default`: every rate as `{\"code\": \"EUR\", \"value\": 0.918456}`. `compact`: plain values, `\"EUR\": 0.918456`.",
+  "enum": [
+    "default",
+    "compact"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the behavioral burden. It usefully discloses that the update interval depends on the subscription plan (daily to minutely), but says nothing about authentication, rate limits, or that the operation is read-only beyond the verb 'Returns'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight paragraphs: the purpose and update-interval caveat come first, then an options summary. The second paragraph is dense but each clause maps to a real parameter, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight optional parameters and no output schema, the description does not explain the response envelope (e.g., rates map, meta timestamps) that an agent would need to interpret results. The per-option explanations partially compensate, but the return structure is left undocumented.

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%, so the schema already documents all eight parameters thoroughly. The description adds a compact narrative of shape, precision, inverse, include, and format but no syntax or constraints beyond what the schema provides, and it omits type and currencies entirely — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — 'Returns the latest exchange rates' — and names the base-currency scope plus the subscription-dependent update interval. It implicitly distinguishes itself from getHistorical and getRate via 'latest', but never explicitly differentiates against the ten sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the word 'latest' and the default USD behavior. There is no explicit guidance on when to pick this over getRate, getHistorical, or getConvert, and no prerequisites or exclusions stated.

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

All fxapi Exchange Rates MCP Server 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