Skip to main content
Glama

Forex Daily Prices

GetForexPrices
Read-only

Get daily price candles for ONE forex currency pair (EUR/USD), newest first: open, high, low, close in the second currency, volume in the first and trades. A day runs midnight to midnight UTC, weekends included; a day without trades has no candle. History goes back to the pair's first trade on the exchange (EUR/USD: 2020). Rates are one exchange's trades, not an interbank or official reference rate, and a day's high or low can hold a stray trade. Plus and Pro also get the day in progress; Free gets a day 4 hours after it ends. GetForexQuote has the latest rate, GetForexIntradayPrices candles within the day, ListForexPairs 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": {
      "pair": "<pair>"
    },
    "name": "GetForexPrices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCurrency pair, e.g. EUR/USD; EURUSD and EUR-USD also work
endDateNoLast UTC day in YYYY-MM-DD format (default: today)
startDateNoFirst UTC day in YYYY-MM-DD format (default: the pair's first trade)
maxResultsNoMaximum days to return, newest first (default: 60, max: 500)

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 only say read-only and closed-world; the description adds day-boundary semantics (midnight-to-midnight UTC, weekends included, gap days have no candle), history depth (2020 for EUR/USD), and a data-quality caveat that highs/lows can hold stray trades and are one exchange's trades rather than an official rate. That is substantive context beyond the annotations.

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?

Front-loaded with the core action and return fields, then caveats, then sibling routing in a single closing sentence. Dense but every clause carries operational information; nothing is padding.

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?

No output schema exists, yet the description enumerates the returned fields (open, high, low, close, volume, trades) and their denominations. Combined with history depth, gap-day behavior, and latency tiers, an agent has everything needed to call and interpret results.

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 baseline is 3, but the description adds meaning the schema lacks: results are newest-first, startDate default reaches back to the pair's first trade (2020 for EUR/USD), and the high/low can be distorted by stray trades. It does not elaborate on format nuances beyond the schema, so it stops short of a 5.

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 daily price candles for ONE forex currency pair') and immediately scopes it against siblings: GetForexQuote for the latest rate, GetForexIntradayPrices for within-day candles, ListForexPairs for the catalog. An agent can pick this tool without opening any schema.

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?

Explicit routing: use GetForexQuote for the latest rate, GetForexIntradayPrices for intraday, ListForexPairs to discover pairs. It also states the one-pair-per-call constraint and the plan-based latency (Free lags 4 hours), which affects when the call is worth making.

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.