Skip to main content
Glama

TickDB Market Data

by io.github.TickDB
OverviewDiscussionsAdmin

get_ticker

Get real-time price snapshots for one or more symbols.

    Returns symbol, last_price and millisecond timestamp. Other fields are conditional,
    including open, prev_close, category, traded value and US extended-hours quotes.
    Crypto statistics use a rolling 24h window; traditional markets use the trading
    day/session. Supports stocks, forex/metals, indices, crypto, CN and HK futures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoProduct type for disambiguation when symbols share the same code across types. Values: stock, crypto, forex, indices, futures. E.g. type='indices' for '000001' = Shanghai Composite vs type='stock' for '000001' = Ping An Bank
symbolsYesComma-separated symbol codes, max 50. E.g. 'XAUUSD,BTCUSDT,AAPL.US'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / symbols / description
      Added value: +"Comma-separated symbol codes, max 50. E.g. 'XAUUSD,BTCUSDT,AAPL.US'"
    • addedInput schema / properties / type / description
      Added value: +"Product type for disambiguation when symbols share the same code across types. Values: stock, crypto, forex, indices, futures. E.g. type='indices' for '000001' = Shanghai Composite vs type='stock' for '000001' = Ping An Bank"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it declares the guaranteed fields (symbol, last_price, millisecond timestamp), flags which fields are conditional, and explains that crypto uses a rolling 24h window while traditional markets use the trading day/session. It omits auth/rate-limit and error behavior, but the return-shape and time-window semantics are meaningful behavioral disclosure beyond the schema.

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?

Front-loads the core purpose in the first sentence, then layers return fields, then timing semantics, then supported assets. Every sentence carries information, though the return-field enumeration is somewhat list-like and could be tightened.

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?

No output schema exists, so the description rightly explains the return values, and with no annotations it covers read semantics and market-specific time windows. It is nearly complete for a snapshot tool; a note on invalid symbols or rate limits would fully close the gap.

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%, so the schema already documents both 'symbols' (comma-separated, max 50) and 'type' (disambiguation values and the 000001 example). The description adds no parameter-level detail beyond this, so baseline 3 applies.

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 real-time price snapshots for one or more symbols.' This clearly distinguishes it from siblings like get_kline (historical candles) and get_order_book. However, it never names a sibling explicitly, so the differentiation is inferential rather than stated.

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 when-to-use guidance and no alternatives are named. It lists supported markets (stocks, forex/metals, indices, crypto, futures) which hints at applicability, but an agent gets no help choosing between get_ticker, get_intraday, get_kline_latest or get_recent_trades.

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