Skip to main content
Glama

Forex Pairs

ListForexPairs
Read-only

List the forex currency pairs with rates, in pair order: pair (EUR/USD), both currencies' names, whether it still trades and its first stored trade date. A rate is the price of one unit of the first currency in the second, from one exchange's trades, not an interbank or official reference rate. currency keeps the pairs that include it. Use GetForexQuote for the latest rate, GetForexPrices for daily candles and GetForexIntradayPrices for candles within the day. Included on every plan.

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": "ListForexPairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoPairs to skip, for the next page (default: 0)
currencyNoISO 4217 currency code, e.g. EUR, to keep the pairs that include it (default: every pair)
maxResultsNoMaximum pairs to return (default: 100, max: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered by structured data. The description adds genuinely non-obvious context: the rate is sourced from a single exchange's trades rather than an interbank or official reference rate, plus 'Included on every plan' for availability. It stops short of noting whether rates are delayed or how stale the latest price may be.

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?

Front-loads the resource and its returned fields, then the rate-definition caveat, then the alternatives, then plan availability — a sensible ordering. It is fairly dense and the rate-definition clause is a long run-on, but every sentence carries information an agent would need.

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 correctly compensates by enumerating the returned fields and defining what a 'rate' means, which is the main ambiguity for this tool. Pagination and limits are left to the schema, and three parameters make the tool simple enough that little else is required.

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 offset, currency, and maxResults are already fully documented, including the default and max of 500. The description restates the currency filter ('currency keeps the pairs that include it') without adding format or edge-case detail beyond the schema's ISO 4217 example. Baseline 3 applies when the schema carries parameter semantics.

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?

Names a specific verb and resource ('List the forex currency pairs with rates') and enumerates the returned fields: symbol (EUR/USD), both currency names, trading status, and first stored trade date. The scope is narrow enough that an agent can distinguish it immediately from GetForexQuote, GetForexPrices, and GetForexIntradayPrices.

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?

Explicitly routes the agent to the alternatives and the condition that selects each: GetForexQuote for the latest rate, GetForexPrices for daily candles, GetForexIntradayPrices for intraday candles, leaving this tool for the pair roster. It also states the filtering behavior for the currency parameter, so there is no ambiguity about which tool to use.

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.