Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_rank_cxg_ths

Read-onlyIdempotent

Retrieve stocks hitting new highs from THS. Select period: monthly, half-year, yearly, or all-time. Use for technical screening.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo创月新高
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source URL and return type, but no further behavioral details like pagination or column specifics.

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?

The description is a compact docstring with title, URL, parameter documentation, and return type. Each line serves a purpose, and it is well-structured and front-loaded.

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?

Given the simple one-parameter tool with no output schema, the description covers the data source, parameter choices, and return type. However, it does not detail the DataFrame's columns or content, which would be helpful since there is no output schema.

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% with only a default value; the description compensates by listing the four valid choices for symbol (创月新高, 半年新高, 一年新高, 历史新高). This adds meaningful guidance beyond the schema's type string.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves stock screening data for '创新高' (new highs) from 同花顺 (THS) data center, with a provided URL. It distinguishes itself from sibling rank tools by specifying this specific category.

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?

The description implies usage for screening stocks hitting new highs, and the parameter choices define time periods, but it does not explicitly state when to use this versus alternative ranking tools or mention 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