Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Historical Candlesticks by Date

history_candlesticks_by_date
Read-onlyIdempotent

Retrieve historical candlestick data for any symbol over a specified date range. Supports multiple time periods and optional adjustments for splits and dividends.

Instructions

Get historical candlestick data by date range. Only symbol is required; period defaults to day (1m/5m/15m/30m/60m/day/week/month/year), forward_adjust to false, trade_sessions to all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd date (yyyy-mm-dd), optional
startNoStart date (yyyy-mm-dd), optional
periodNoPeriod: 1m, 5m, 15m, 30m, 60m, day, week, month, year (default: day)day
symbolYesSecurity symbol, e.g. "700.HK"
forward_adjustNoWhether to forward-adjust for splits/dividends (default: false / no adjust)
trade_sessionsNoTrade sessions: "intraday" (regular hours only) or "all" (include pre-market and post-market; default "all")all

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv0.10.2
    • addedInput schema / properties / forward_adjust / default
      Added value: +false
    • changedInput schema / properties / forward_adjust / description
      Previous value: -"Whether to forward-adjust for splits/dividends"New value: +"Whether to forward-adjust for splits/dividends (default: false / no adjust)"
    • addedInput schema / properties / period / default
      Added value: +"day"
    • changedInput schema / properties / period / description
      Previous value: -"Period: 1m, 5m, 15m, 30m, 60m, day, week, month, year"New value: +"Period: 1m, 5m, 15m, 30m, 60m, day, week, month, year (default: day)"
    • addedInput schema / properties / trade_sessions / default
      Added value: +"all"
    • changedInput schema / properties / trade_sessions / description
      Previous value: -"Trade sessions: \"intraday\" (regular hours only) or \"all\" (include pre-market and post-market)"New value: +"Trade sessions: \"intraday\" (regular hours only) or \"all\" (include pre-market and post-market; default \"all\")"
    • changedInput schema / required
      Previous value: -[
-  "symbol",
-  "period",
-  "forward_adjust",
-  "trade_sessions"
-]New value: +[
+  "symbol"
+]
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"HistoryCandlesticksByDateParam"
  3. Addedv0.4.5
  4. Removedv0.4.0
  5. Addedv0.3.2
  6. Removedv0.3.1
  7. First observedv0.1.12

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds some context by noting that only symbol is required and by listing default values, but it does not disclose output format, date range limits, timezone behavior, or other runtime traits. Overall it adds modest value beyond the annotations.

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?

The description is a single well-structured sentence that front-loads the main purpose and then packs the essential defaults efficiently. Every part contributes useful information without redundancy.

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?

For a read-only data retrieval tool with six documented parameters, the description covers the basic call requirements. However, it does not clarify how this tool differs from sibling candlestick/history tools, and with no output schema it leaves the return shape implicit.

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 100%, so the schema already documents all parameters. The description restates defaults for period, forward_adjust, and trade_sessions but does not add meaningful detail beyond the schema, such as value constraints, date formats, or edge-case behavior.

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?

The description clearly states a specific action ('Get historical candlestick data by date range') and identifies the key resource and inputs. It is distinguishable from the likely sibling 'history_candlesticks_by_offset' via the 'by date range' phrasing, though it does not explicitly name that sibling.

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?

The description provides useful defaults but gives no guidance on when to choose this tool over alternatives such as history_candlesticks_by_offset or candlesticks. No exclusions or conditions are mentioned.

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/longbridge/longbridge-mcp'

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