Skip to main content
Glama

TickDB Market Data

by io.github.TickDB
OverviewDiscussionsAdmin

get_kline_latest

Get the most recent (live/incomplete) K-line candle for one or more symbols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoProduct type for disambiguation: stock, crypto, forex, indices, futures
adjustNoStock price adjustment: none (default), forward, backward; US/HK/CN stocks
symbolsYesComma-separated symbol codes, max 50. E.g. 'AAPL.US,TSLA.US'
intervalYesCandle interval: 1m 3m 5m 15m 30m 1h 2h 4h 1d 1w 1M

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / adjust
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stock price adjustment: none (default), forward, backward; US/HK/CN stocks",
+  "title": "Adjust"
+}
    • addedInput schema / properties / interval / description
      Added value: +"Candle interval: 1m 3m 5m 15m 30m 1h 2h 4h 1d 1w 1M"
    • addedInput schema / properties / symbols / description
      Added value: +"Comma-separated symbol codes, max 50. E.g. 'AAPL.US,TSLA.US'"
    • addedInput schema / properties / type / description
      Added value: +"Product type for disambiguation: stock, crypto, forex, indices, futures"
  2. First observed

TDQS

A3.5/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 the full burden. It does disclose one genuinely useful behavioral trait — the returned candle is live/incomplete and therefore mutating in value — but says nothing about auth requirements, rate limits, whether data refreshes, or what fields a candle contains.

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?

A single front-loaded sentence with no filler; every word contributes to describing the operation and its distinguishing characteristic.

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 data-returning tool with no output schema and no annotations, the description covers the input side adequately but leaves the return shape wholly unexplained — an agent cannot tell what fields a 'candle' contains (OHLCV, timestamp, symbol grouping for multiple symbols). It stops at minimum viable.

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 description coverage is 100%, with symbols, interval, type, and adjust all documented inline (including examples and valid interval values), so the schema does the heavy lifting. The description adds nothing about parameter semantics, so the baseline of 3 is appropriate.

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 ('Get the most recent ... K-line candle') and scopes it to one or more symbols. The '(live/incomplete)' qualifier implicitly distinguishes it from the historical get_kline sibling, but it never names that alternative, so the differentiation is implied rather than explicit.

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?

The phrase 'most recent (live/incomplete)' hints at the right context (real-time/latest snapshot rather than historical retrieval), but there is no explicit 'use this when' guidance and no mention of the sibling get_kline to route between them. Usage is implied, not stated.

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

All TickDB Market Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources