get_kline_intervals
List all supported K-line candlestick interval strings.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
TickDB Market Data
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It accurately describes the tool as listing interval strings, but does not disclose any potential dependencies or side effects. For a read-only listing, this is adequate but minimal.
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 sentence with no wasted words. It is perfectly concise and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters, no output schema, and simple behavior, the description is complete enough. It could mention the return format (e.g., array of strings), but it is not essential for this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters (0 params, schema coverage 100%). With zero parameters, the baseline is 4, and the description adds no additional param info, which is fine.
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 lists supported K-line candlestick interval strings. It uses specific verb 'list' and resource 'supported K-line candlestick interval strings', distinguishing it from siblings like get_kline (fetches data) and get_kline_latest (latest kline).
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 implies usage context: to retrieve available intervals before querying kline data. It does not explicitly exclude alternatives, but given sibling tools, the context is clear.
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.