Skip to main content
Glama
InvestBrain

InvestBrain

tushare_get_market_top_movers

Retrieve daily top gainers, losers, and most active stocks for a given trade date to review market performance and identify movers.

Instructions

Get top gainers/losers for the day (Tushare API: top_list).

Args:
    trade_date: Trading date in YYYYMMDD format (default: today)

Returns:
    dict: Top gainers, losers, and most active stocks

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tushare_get_market_top_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
trade_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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, and it falls short: nothing about Tushare token/authentication requirements (notable given the sibling tushare_check_token_status), rate limits, or how many rows 'top' returns. The brief Returns line ('top gainers, losers, and most active stocks') is the only behavioral disclosure, and it slightly expands on the summary line.

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?

Short and front-loaded: purpose first, then Args and Returns. The Args/Returns scaffolding is slightly verbose for one optional parameter but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter data fetch with no output schema, the description covers the purpose, parameter format, and rough return shape. It is still thin on authentication context and on what 'top' quantifies, which an agent would need to call it confidently.

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?

The single parameter has 0% schema description coverage, so the description must compensate — and it does, specifying the YYYYMMDD format and the 'default: today' behavior. That fully covers the only parameter, leaving little room for improvement.

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 top gainers/losers for the day') and even names the underlying Tushare endpoint (top_list), so the agent knows it is a daily market-mover snapshot. It does not, however, contrast itself with siblings such as market_get_market_sentiment or market_get_stock_quote, so disambiguation relies on the name alone.

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 never says when to pick this over the many sibling quote/sentiment tools, nor does it state any prerequisites or exclusions. The only usage signal is the implied 'for the day' scope.

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