Skip to main content
Glama
Sign In
TradeTrack MCP

TradeTrack MCP

by BukeLy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Tradetrack

tradetrack
Read-onlyIdempotent

Fetch HSBC stock rankings for US or Hong Kong markets by list (hot, top buy, top sell, top hold) and period to track trending trader activity.

Instructions

Latest HSBC TradeTrack lists for a market. lists defaults to all four.

period picks the ranking window: today, yesterday or last_month for every list; last_3_months and last_6_months for top_hold only.

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>"
    },
    "name": "tradetrack"
  }
}

Input Schema

NameRequiredDescriptionDefault
listsNo
marketYes
periodNotoday

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description goes beyond them by disclosing the `lists` default behaviour and an important cross-parameter constraint (last_3_months/last_6_months apply only to top_hold), which is not expressible in 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core purpose front-loaded, followed by the two non-obvious parameter rules. No filler, every clause carries information.

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 no explanation, and the parameter semantics and default behaviour are well covered for a 3-param tool. The main shortfall is the absence of any routing guidance relative to tradetrack_history.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it largely does: it documents the default for `lists` and explains that `period` selects the ranking window, including which values are valid for which list. Only `market` is left unaddressed, and its US/HK enum is self-explanatory.

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 resource (latest HSBC TradeTrack lists), scope (per market), and implies the time dimension with 'Latest'. It is clear what the tool returns, though it never mentions the sibling tradetrack_history, so the boundary between 'latest' and 'history' is left to inference.

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?

Usage is only implied: 'Latest' nudges the agent toward this tool over tradetrack_history for current data, but there is no explicit when-to-use statement, no exclusion, and the alternative is never named. Adequate but with a clear gap.

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