Skip to main content
Glama

Forex Intraday Prices

GetForexIntradayPrices
Read-only

Get price candles within the day for ONE forex currency pair (EUR/USD), newest first: open, high, low, close in the second currency, volume in the first and trades, around the clock. interval is any whole minutes from 1min (default) to 240min, or 1hour to 4hour, counted from midnight UTC. Defaults to the last 7 days (30 for hourly); startDate and endDate set another, back to the pair's first trade. A period without trades has no candle. A cut answer names the next endTime. Candles are added some minutes after they end; the answer says how far they reach. Plus reads a candle 15 minutes after it ends, Free gets an upgrade note. Rates are one exchange's trades. GetForexPrices has daily candles, GetForexQuote the latest rate.

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

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)
endTimeNoReturn only candles that start before this RFC 3339 time; replaces endDate
intervalNoCandle size: whole minutes from 1min to 240min (e.g. 5min, 15min), or 1hour to 4hour (default: 1min)1min
startDateNoFirst UTC day in YYYY-MM-DD format (default: 7 days before the end, 30 for hourly intervals)
maxResultsNoMaximum candles to return, newest first (default: 60, max: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only and non-destructive; the description adds the operational traits an agent actually needs: candles are appended some minutes after they end, the response declares how far data reaches, Plus reads a candle 15 minutes after it ends while Free gets an upgrade note, a period without trades yields no candle, a truncated response names the next endTime for continuation, and rates come from a single exchange's trades.

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-loaded with the purpose sentence, and essentially every subsequent sentence carries new operational information with no filler. The telegraphic packing ('Plus reads a candle 15 minutes after it ends, Free gets an upgrade note') makes a couple of clauses dense enough to require a second read, which costs a point but not the substance.

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 six parameters, no output schema and only safety annotations, the description carries its weight: it covers the return shape and ordering, date/interval defaults and their change with interval size, missing-candle behavior, truncation/continuation, data latency, and plan-based delays. An agent could call this correctly without opening any other field.

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 schema already carries the per-parameter definitions. The description still adds meaning beyond it: intervals are 'counted from midnight UTC', startDate can reach back to 'the pair's first trade', the 7-day vs 30-day default distinction is restated as behavior rather than a schema default, and the truncated-answer/endTime hint explains what to do when maxResults cuts the result set.

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 price candles within the day for ONE forex currency pair'), then enumerates the returned fields (open, high, low, close, volume, trades) and ordering (newest first). The 'ONE pair' constraint and 'within the day' scope immediately separate it from GetForexPrices (daily) and GetForexQuote (latest rate), both of which it names.

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

Usage Guidelines4/5

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

The closing sentence explicitly routes the agent: daily candles go to GetForexPrices, the latest rate goes to GetForexQuote, so the intraday niche is clear. It never states an explicit when-not condition or prerequisites, and the routing is compressed into the final sentence rather than given as a condition ('use X when Y'), but the context for choosing this tool is unambiguous.

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.