Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_hk_hot_rank_em

Read-onlyIdempotent

Retrieve Hong Kong stock popularity rankings from Eastmoney's investor community to identify trending stocks and gauge market sentiment.

Instructions

东方财富-个股人气榜-人气榜-港股市场 https://guba.eastmoney.com/rank/ :return: 人气榜 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the source URL and confirms it returns a pandas DataFrame, but does not disclose any additional behavioral traits like data freshness, pagination, or rank criteria.

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 very brief, containing only the title, URL, and return type. It is front-loaded and has no fluff, but it is so terse that it reads more like a header than an explanatory description. Still, every line conveys something.

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 read-only tool with no inputs and a clear return type, the description provides the basic purpose. However, it does not explain how this ranking differs from related HK hot rank tools (e.g., latest, detail), and the output content is unspecified beyond '人气榜'. Given the open world hint and absence of an output schema, more context would be helpful.

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 tool takes zero parameters, and the schema coverage is 100%. Per the baseline for 0-param tools, the description does not need to elaborate on parameters; the description's mention of return type adds minor value.

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 the Eastmoney individual stock popularity ranking for the Hong Kong market, including a source URL and return type. However, it lacks an explicit action verb like 'get' or 'list', relying on the tool name to convey the operation. It distinguishes from siblings by specifying '港股市场'.

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 provides no guidance on when to use this tool versus alternative tools such as stock_hk_hot_rank_latest_em or stock_hk_hot_rank_detail_em. There is no mention of exclusions, preferred scenarios, or related tools.

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