get_kline_latest
Get the most recent (live/incomplete) K-line candle for one or more symbols.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| symbols | Yes | ||
| interval | Yes |
TickDB Market Data
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description states 'live/incomplete' but omits behavioral details such as return format, error handling, rate limits, or auth requirements.
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?
Single sentence, no waste, but so brief it sacrifices completeness; fits within constraints but could benefit from more structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations; description fails to explain return values, potential errors, or usage nuances, leaving significant gaps for a real-time data tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, description adds only 'one or more symbols' but no detail on parameter formats (e.g., comma-separated symbols) or interval values.
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?
Description uses specific verb 'Get' and resource 'most recent (live/incomplete) K-line candle', clearly distinguishing from sibling 'get_kline' which likely provides historical completed candles.
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?
Implies usage for obtaining the latest live candle but lacks explicit when-to-use vs alternatives like 'get_kline' or 'get_kline_intervals', and no when-not-to-use guidance.
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.