Skip to main content
Glama

TickDB Market Data

by io.github.TickDB
OverviewDiscussionsAdmin

get_recent_trades

Get the most recent executed trades for a symbol.

    Returns trade id, price, quantity, side (buy/sell/neutral), and timestamp in ms.
    Futures may also return open_interest_change and position_effect
    (long_open, short_open, both_open, long_close, short_close, both_close,
    long_transfer, short_transfer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoProduct type for disambiguation: stock, crypto, forex, indices, futures
limitNoNumber of trades, default 100, max 1000
symbolYesSingle symbol. Supported: US/HK/CN stocks, CN/HK futures and crypto. E.g. 'AAPL.US', '700.HK', '600519.SH', or 'BTCUSDT'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Number of trades, default 100, max 1000"
    • addedInput schema / properties / symbol / description
      Added value: +"Single symbol. Supported: US/HK/CN stocks, CN/HK futures and crypto. E.g. 'AAPL.US', '700.HK', '600519.SH', or 'BTCUSDT'"
    • addedInput schema / properties / type / description
      Added value: +"Product type for disambiguation: stock, crypto, forex, indices, futures"
  2. First observed

TDQS

B3.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 the full behavioral burden. It does disclose the return shape (trade id, price, quantity, side, timestamp ms) and futures-only extras with their value enumerations, which is genuinely useful. However, it says nothing about rate limits, data freshness/latency, market-session dependence, or permissions — meaningful gaps for a no-annotation tool.

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 enumerates returns compactly. The parenthetical enumeration of position_effect values is slightly heavy but earns its place since there is no output schema.

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?

With no output schema, the description usefully documents the returned fields and futures-specific extensions, which an agent needs. It falls short only on operational context such as pagination beyond limit, data freshness, and error/empty-result behavior.

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 symbol, type, and limit (default 100, max 1000) are already fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 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 recent executed trades) scoped to a single symbol, which clearly separates it from quote-style siblings like get_ticker or get_kline. It does not explicitly name an alternative tool, so the differentiation is implied rather than asserted.

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?

The description gives no guidance on when to use this instead of related siblings (get_ticker, get_intraday, get_order_book, get_kline). There is no mention of prerequisites, data availability, or the conditions under which recent trades are the right choice.

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