Skip to main content
Glama

Forex Quote

GetForexQuote
Read-only

Get the latest rate of forex currency pairs (EUR/USD, USD/JPY), up to 25 a call: last trade price and its UTC time, the 24-hour change, and the 24-hour volume (in the first currency), high and low. Rates are one exchange's trades, not an interbank or official reference rate; for official daily rates use GetEconomicIndicator. A thinly traded pair shows an old last-trade time; that is its real last trade. A pair asked the other way round (USD/EUR) answers with the listed pair. Pro reads real time, Plus 15 minutes delayed, Free gets an upgrade note (daily candles are in GetForexPrices). ListForexPairs lists the pairs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pairs": "<pairs>"
    },
    "name": "GetForexQuote"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairsYesCurrency pairs (max 25), e.g. EUR/USD, GBPUSD, USD-JPY

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish a safe read-only operation, and the description adds substantial context beyond them: rates are from one exchange rather than an interbank reference, thinly traded pairs show a genuinely old last-trade time, inverse pair requests answer with the listed pair, and call limit is 25 pairs. This is exactly the kind of nuance an agent needs to interpret results correctly.

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?

The paragraph is dense but front-loaded with the core purpose and return fields, then moves to important caveats and alternatives. Every sentence carries operational meaning, including the exchange-source caveat, stale-trade explanation, inverse-pair behavior, and tier delays.

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 no output schema, the description still explains the returned fields and their units (volume in the first currency, UTC time). It also covers the key behavioral edge cases and tier limitations, leaving no major gap for an agent invoking a one-parameter quote 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%, so the basic pair format and max-25 limit are already documented. The description still adds semantic value by explaining that a reversed pair like USD/EUR will answer with the listed pair, which affects how the agent should interpret the response. It restates the 25-pair cap already in the schema but does not waste space.

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?

States a specific verb and resource ('Get the latest rate of forex currency pairs') and enumerates exactly what is returned: last trade price and UTC time, 24-hour change, 24-hour volume, high and low. It explicitly distinguishes itself from GetForexPrices (daily candles), GetEconomicIndicator (official rates), and ListForexPairs (pair listing).

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

Usage Guidelines5/5

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

Gives explicit routing: use GetEconomicIndicator for official daily rates and GetForexPrices for daily candles, with ListForexPairs for pair discovery. It also states tier behavior (Pro real time, Plus 15-minute delay, Free upgrade note), which tells the agent when this tool will return useful versus degraded data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.