Skip to main content
Glama

TickDB Market Data

by io.github.TickDB
OverviewDiscussionsAdmin

get_capital_flow

Get capital flow (money flow) analysis for a stock.

    Returns intraday flow timeline and breakdown of capital inflows/outflows
    by order size: large, medium, and small. All timestamps in this response
    are Unix seconds, unlike the millisecond timestamps in most market tools.
    Supported: US stocks, Hong Kong stocks, A-shares.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoProduct type for disambiguation: stock, crypto, forex, indices
symbolYesSingle stock code. E.g. '700.HK' or 'AAPL.US'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / symbol / description
      Added value: +"Single stock code. E.g. '700.HK' or 'AAPL.US'"
    • addedInput schema / properties / type / description
      Added value: +"Product type for disambiguation: stock, crypto, forex, indices"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose a genuinely important gotcha — timestamps are Unix seconds here versus milliseconds in most market tools — and describes the shape of the result (intraday timeline plus order-size breakdown). It omits auth/permission needs, rate limits, and any freshness or history-window limits.

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-loaded with the one-line purpose, followed by return-shape and timestamp notes in a compact block. No filler sentences, though the phrasing is slightly loose 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?

With no output schema, the description does the work of describing the return (intraday timeline and large/medium/small breakdown) and flags the unit discrepancy. Supported markets are covered. Missing only edge behavior such as empty results, history depth, or rate limits for a live-data endpoint.

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 both parameters are already documented (symbol format '700.HK'/'AAPL.US', type disambiguation list). The description adds nothing about parameters beyond the implicit stock context, making the baseline 3 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 capital flow (money flow) analysis for a stock,' and even supplies the synonym 'money flow' to aid matching. It also enumerates what comes back (intraday flow timeline, inflow/outflow by order size). However, it never contrasts itself with close neighbors like get_intraday or get_order_book, so the agent must infer the distinction.

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?

'Supported: US stocks, Hong Kong stocks, A-shares' gives a clear applicability constraint on the input. There is no explicit when-to-use guidance or named alternative for overlapping tools (intraday, order book, recent trades), so usage is implied rather than directed.

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