Skip to main content
Glama
Sign In

fxapi Exchange Rates MCP Server

by com.fxapi.api
OverviewDiscussionsAdmin

Cross rates between several currencies

getMatrix

Returns every cross rate between 2 to 25 currencies in one request: data.EUR.USD is the price of 1 EUR in USD. Latest at your plan's update interval, or the close of a past date. format=csv gives the table with one row per base currency.

Input Schema

NameRequiredDescriptionDefault
dateNoThe close of this past day (format `YYYY-MM-DD`).
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`.
precisionNoRound every value to this many decimals (0 to 10). By default values carry up to 10 decimals (10 significant digits below 0.1).
currenciesYes2 to 25 currency codes, comma-separated (e.g. `USD,EUR,GBP`) or as `currencies[]=`. Rows and columns keep this order.

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. Added

TDQS

A3.7/5.0
Behavior4/5

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

Only a title is provided as annotation, so the description carries the burden and does well: it discloses the matrix return shape (`data.EUR.USD` = price of 1 EUR in USD), that data is latest at the plan's update interval or a past-date close, and that formats produce different table shapes. It does not mention rate limits, error behavior for invalid codes, or response envelope details beyond the example.

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?

Three tight sentences, front-loaded with the core purpose and followed by the return-shape example and format nuance. No filler, though the csv detail slightly overlaps what the schema already says.

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?

With no output schema, the description adequately explains the matrix return shape and date/format behavior for a 4-parameter read tool. Minor gaps remain around error handling and envelope structure, but an agent has enough to invoke it correctly.

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 coverage is 100% and every parameter is well documented in the schema (date format, format enum behavior, precision range, currency list). The description adds little parameter meaning beyond reiterating the 2-25 currency bound and the csv row-per-base-currency behavior, so 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?

States a specific verb and resource: returns every cross rate between 2 to 25 currencies in one request, and explains the matrix orientation with `data.EUR.USD`. It is clearly a bulk cross-rate tool rather than a single-pair tool, though it never names the sibling tools (getRate, getConvert, getLatest) it should be chosen over.

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?

It implies when to use the tool ('Latest at your plan's update interval, or the close of a past `date`') and its 2-25 currency scope, which implicitly separates it from a single-pair lookup. However there is no explicit guidance on when to prefer this over getRate, getConvert, or getLatest, leaving the routing inference up to the agent.

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