Skip to main content
Glama
Sign In

FinzData market data

by io.github.FinzData
OverviewDiscussionsAdmin

Get FX (currency) bars

get_fx
Read-onlyIdempotent

Answers 'what did EURUSD (or USDJPY) do?' Give a symbol (currency pair, e.g. EURUSD) and optionally interval (1min, 5min, 15min, 30min, 1hour or 1day, default 1day) plus start and end. Returns OHLC bars, times in US Eastern, clipped to as_of. Covers 79 currency pairs (EURUSD, USDJPY, GBPUSD and more) since January 2010. Free keys get daily bars for the last 12 months; paid keys get every bar size.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_fx"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
as_ofNoPoint-in-time cutoff (YYYY-MM-DD). Nothing dated after this is returned, preventing look-ahead bias. Defaults to today (UTC).
startNo
symbolYesCurrency pair, e.g. EURUSD or USDJPY.
intervalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: OHLC return shape, US Eastern timestamps, clipping to as_of, 79-pair coverage since January 2010, and the free-vs-paid tier limits. That tier/coverage information is the kind of context annotations cannot express.

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 purpose as a question, then parameters, then return format, then coverage/limits — a sensible order with no filler sentences. Minor redundancy: EURUSD is repeated three times as an example.

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?

There is no output schema, and the description does cover the return contract (OHLC bars, US Eastern, clipped to as_of) plus data coverage and access tiers. The remaining gap is the default date range when start/end are omitted, which an agent would need to call it confidently.

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 only 40%, and the description partially compensates: it enumerates every interval value plus the non-obvious default of 1day, and explains that output is clipped to as_of. However, start and end are only mentioned in passing with no format or default-range semantics, leaving two undocumented parameters unclarified.

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?

Opens with the exact question it answers ('what did EURUSD do?') and states it returns OHLC bars for currency pairs, which cleanly separates it from asset-class siblings like get_crypto, get_futures, and get_index. It never names a sibling explicitly, so the differentiation is by asset class rather than direct routing.

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?

Tells the agent what to supply (symbol required, interval/start/end optional) and adds a real usage constraint: free keys only get daily bars for the last 12 months, paid keys get every bar size. It gives no explicit when-to-use-this-vs-get_bars guidance and doesn't state what happens if start/end are omitted.

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

All FinzData market data 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