Skip to main content
Glama
Sign In
TradeTrack MCP

TradeTrack MCP

by BukeLy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Tradetrack History

tradetrack_history
Read-onlyIdempotent

Retrieves historical intraday snapshots of HSBC's public trending stock lists for US or Hong Kong markets, filtered by date range, list type, or symbol, to track changes over time.

Instructions

Past intraday snapshots of the "today" lists, one per HSBC refresh, oldest first, collected since 2026-10-16.

Dates are trading days (market-local), inclusive, at most 31 days per call. Pass symbol to keep only snapshots that contain that stock (HK codes may omit leading zeros). Days without trading return nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>",
      "date_from": "<date_from>"
    },
    "name": "tradetrack_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
listsNo
marketYes
symbolNo
date_toNo
date_fromYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, so the safety profile is covered. The description adds genuinely new traits beyond that: oldest-first ordering, the 31-day window cap, the data collection start date, and that non-trading days yield no results.

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?

Three dense sentences with no filler; the core scoping constraint (past snapshots, one per refresh) is front-loaded. Slightly cluttered by the parenthetical HK note but nothing is wasted.

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 an output schema present, return values need not be described, and annotations cover the safety profile. The remaining gap is that the `lists` filter and its enum are unexplained, and the relationship to the sibling tradetrack is left implicit.

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 0%, so the description must carry the burden. It clarifies `symbol` (HK codes may omit leading zeros) and the date parameters (trading days, inclusive, 31-day max), and 'market-local' implies `market` values. But `lists` and the enum values (hot/top_buy/top_sell/top_hold) and US/HK enumeration receive no explanation.

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?

The description names a specific resource ('past intraday snapshots of the "today" lists') and an explicit verb-like framing, plus a collection start date. It implicitly contrasts with the sibling tradetrack (current vs. historical), though it never names the sibling to make the routing 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?

It gives operational constraints (trading-day dates, inclusive, at most 31 days per call, empty days return nothing) that tell the agent how to call it. However, it never states when to use this tool instead of the sibling tradetrack, leaving the historical-vs-live choice to inference.

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

Deploy Server

Other Tools