Skip to main content
Glama
florinel-chis

bvb-mcp

get_candles

Read-only

Fetch OHLCV candles for a Bucharest Stock Exchange ticker. Returns historical open, high, low, close, and volume data with adjustable time window and resolution.

Instructions

Fetch OHLCV candles for a BVB ticker.

Returns bars oldest-first, each {time, open, high, low, close, volume} where time is an ISO 8601 UTC timestamp and volume is an integer. An empty list means the datafeed had no data for the window (not an error).

The window is resolved as: to defaults to now; countback (when given) fixes the number of bars, otherwise it is derived from the from_/to span (capped at 5000) or defaults to 300; from_ defaults to to minus countback bars. Daily bars reach back to the 1990s; intraday resolutions only cover a recent window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoWindow end, unix seconds (UTC). Defaults to now.
from_NoWindow start, unix seconds (UTC). Derived from countback if omitted.
tickerYesBVB ticker, e.g. "TLV", "SNP", or an index like "BET".
adjustedNoSplit/dividend-adjusted prices (True) or raw (False).
currencyNoQuote currency code, e.g. 'RON'.RON
countbackNoNumber of bars ending at 'to'. Overrides the from/to span when set; derived from the span (or defaults to 300) otherwise.
resolutionNoBar size (case-insensitive). Minutes: 1, 5, 15, 30, 60. Daily: 1D (or D). Weekly: 1W. Monthly: 1M.1D

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds value by detailing return format (oldest-first), empty list behavior, and window resolution logic. It does not contradict annotations and provides context beyond what annotations convey.

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?

The description is reasonably concise, with a clear structure that separates return format from window resolution logic. It could be slightly more structured (e.g., bullet points), but it remains focused and front-loaded with the purpose.

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?

Given 7 parameters, high schema coverage, and an output schema, the description covers essential behaviors including return format, edge cases (empty list), and window resolution. It is complete for the tool's complexity.

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?

Schema descriptions cover all 7 parameters at 100%. The description adds significant meaning by explaining the window resolution algorithm, default behaviors for to, countback, from_, and how they interact, which goes beyond the schema descriptions.

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 fetches OHLCV candles for a BVB ticker, specifying the return format and behavior when no data. It distinguishes itself from sibling tools like get_symbol_info or list_instruments by focusing on candlestick data.

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 description explains the window resolution logic in detail, including defaults and how parameters interact. However, it does not explicitly state when to use this tool over alternatives like get_fundamentals or search_symbol, so it misses explicit exclusions or alternatives.

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/florinel-chis/bvb-mcp'

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