Skip to main content
Glama

get_bars

Retrieve ordered OHLCV candles for a symbol across an inclusive UTC time range, enabling charting and historical price analysis of NSE market data.

Instructions

Return ordered OHLCV candles for one symbol and an inclusive UTC time range.

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": {
      "arguments": "<arguments>"
    },
    "name": "get_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes

Output Schema

NameRequiredDescriptionDefault
barsYes
returned_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only discloses that results are ordered and the range is inclusive in UTC. It says nothing about ordering direction (ascending vs descending), what happens when the requested range exceeds the limit cap in the schema, whether results are truncated or error out, or behavior for unlisted symbols.

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?

A single front-loaded sentence with no filler; the resource and its scoping constraints come first. It is arguably too terse for a four-field ranged query, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not needed, and the core contract (symbol + inclusive UTC range) is stated. Gaps remain around truncation/cap behavior and ordering guarantees, which matter for a candle-fetching tool with a hard limit parameter.

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?

Top-level reported schema coverage is 0%, but the nested argument definitions do describe symbol, start/end timestamps and the limit cap; the description reinforces 'one symbol' and 'inclusive UTC time range', matching three of the four fields. It adds no meaning for limit or for what 'ordered' means in practice, so it only partially compensates.

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?

States a specific verb and resource ('Return ordered OHLCV candles') plus scope ('one symbol and an inclusive UTC time range'), which is clearly distinguishable from the sibling stats/indicator tools. It does not explicitly name or contrast a sibling, so it stops short of a 5.

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?

There is no when-to-use guidance, no mention of when not to use it, and no pointer to alternatives such as compute_indicators or get_price_extremes for derived values. The agent must infer that this is the raw-candle retrieval primitive from the name alone.

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