Skip to main content
Glama
major7apps

tiingo-mcp

by major7apps

get_forex_prices

Retrieve historical forex prices for any currency pair, with options to set date range and resample frequency.

Instructions

Get historical forex prices for a currency pair.

Args: ticker: Currency pair (e.g. eurusd, gbpusd, usdjpy). start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format. resample_freq: Resample frequency — 1min, 5min, 15min, 30min, 1hour, 1day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
end_dateNo
start_dateNo
resample_freqNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description only says 'Get historical forex prices' without explicitly stating it's a read-only operation or disclosing any behavioral traits like rate limits or authentication needs.

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?

Concise single paragraph with a list of parameters; front-loaded purpose, no redundant sentences.

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?

Covers all parameters with examples and format; output schema exists so return values are not needed; minor omission of error conditions or data availability but overall adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by explaining each parameter: ticker examples, date format, and resample_freq enumeration, adding crucial meaning beyond the schema.

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 it gets historical forex prices for a currency pair, distinguishing it from siblings like get_forex_quote (realtime) and get_crypto_prices.

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?

No explicit guidance on when to use this tool versus alternatives; the purpose implies historical forex but lacks when-not conditions or alternative tool mention.

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/major7apps/tiingo-mcp'

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