Skip to main content
Glama
SiftingIO

siftingio-mcp

Official

Forex OHLC bars

forex_bars
Read-only

Retrieve historical OHLC bars for forex pairs like EURUSD. Specify pair, date range, and interval (1m-1h) to get open, high, low, close data with pageable results.

Instructions

Historical OHLC bars for a 6-char FX pair (e.g. EURUSD). Volume is always 0 for OTC spot forex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairYes6-character FX pair, e.g. EURUSD.
startYesInclusive lower bound, YYYY-MM-DD or RFC3339 (UTC). Required.
endNoInclusive upper bound. Default: now.
intervalNoBar interval. Default 1m.
cursorNoOpaque pagination cursor.
limitNoPage size.
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds a specific behavioral trait: volume is always 0 for OTC spot forex, which is beyond annotations. No contradictions.

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?

Two sentences, front-loaded with purpose, no wasted words. Perfectly concise.

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?

Given read-only annotation and no output schema, the description covers core purpose and a key data trait (volume zero). Pagination and return format are in schema, so completeness is adequate for a simple data tool.

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 parameters are well-documented. The description adds little beyond schema (only example pair and volume note). Baseline 3 is appropriate.

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?

The description clearly states the tool retrieves historical OHLC bars for a 6-character FX pair, using specific verb 'historical' and resource 'bars'. It distinguishes from sibling tools like crypto_bars and stocks_bars by specifying forex.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. While it mentions volume is always 0, it does not compare to crypto_bars or stocks_bars or provide conditions for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SiftingIO/siftingio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server