get_kline
Get historical K-line (OHLCV candlestick) data for a symbol.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| limit | No | ||
| symbol | Yes | ||
| end_time | No | ||
| interval | Yes | ||
| start_time | No |
TickDB Market Data
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only states it returns historical data, implying a read-only operation, but fails to mention any constraints like rate limits, pagination, or required authentication.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, front-loading the key action. However, it is arguably too terse for a tool with 6 parameters; it sacrifices necessary detail for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (6 parameters, no output schema, no annotations), the description is highly incomplete. It lacks explanation of return format, parameter constraints, and use cases, leaving the agent with insufficient information to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the tool description adds no parameter details beyond the parameter names. It does not explain what 'interval', 'limit', 'start_time', 'end_time', or 'type' mean or how they affect results.
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 verb 'Get', the resource 'historical K-line (OHLCV candlestick) data', and the scope 'for a symbol'. It effectively distinguishes from sibling tools like get_kline_latest and get_kline_intervals.
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 usage guidance is provided. The description does not indicate when to use this tool over alternatives or any prerequisites. It lacks context for appropriate use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct data type or operation (e.g., symbol discovery, capital flow, intraday, kline, order book, trades). No two tools have overlapping purposes, and descriptions clearly differentiate them.
Naming Consistency5/5
All tools follow a consistent 'get_' prefix followed by a descriptive noun (e.g., get_available_symbols, get_intraday, get_kline). No mixing of conventions or vague verb usage.
Tool Count5/5
13 tools is well-scoped for a market data server. Each tool serves a specific need without unnecessary redundancy, covering discovery, real-time, historical, and reference data.
Completeness4/5
The tool set covers core market data needs: discovery, real-time quotes, historical kline, depth, trades, capital flow, metrics, trading calendar, and sessions. Minor gaps exist (e.g., corporate actions, historical trade list), but the primary workflows are supported.