Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_rank_cxd_ths

Read-onlyIdempotent

Retrieve lists of stocks hitting new lows across monthly, half-year, yearly, or historical periods. Get detailed technical screening data from THS (同花顺) to identify bearish market conditions.

Instructions

同花顺-数据中心-技术选股-创新低 https://data.10jqka.com.cn/rank/cxd/ :param symbol: choice of {"创月新低", "半年新低", "一年新低", "历史新低"} :type symbol: str :return: 创新低数据 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo创月新低
Behavior2/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. However, the description adds no behavioral context beyond stating it returns a pandas DataFrame; there is no mention of data freshness, pagination, rate limits, or any caveats.

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?

The description is compact and structured, with a clear title, source URL, parameter documentation, and return type. It avoids unnecessary verbosity, though it could be more informative without becoming bloated.

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 simple one-parameter read-only tool, the description covers the key filter options, but the return description '创新低数据' is vague and does not specify what columns or data elements are included. With no output schema, this leaves some ambiguity about the result structure.

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 schema provides only a string type with a default value and no descriptions (0% coverage). The description compensates by listing the valid choices for the 'symbol' parameter: 创月新低, 半年新低, 一年新低, 历史新低, which is essential for correct invocation.

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 clearly identifies the tool as THS data center technical stock selection for new lows, with a specific URL. The title '创新低' (new lows) distinguishes it from sibling rank tools like stock_rank_cxg_ths (创新高). The purpose is evident, though it lacks an explicit verb like 'list' or 'get'.

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?

No guidance is provided on when to use this tool versus alternative ranking tools or other data sources. The description only includes parameter documentation and a URL, with no mention of use cases, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevynf/akbridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server