Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_hk_hot_rank_latest_em

Read-onlyIdempotent

Fetches the current popularity ranking for a Hong Kong stock from Eastmoney, using the provided symbol to identify the stock and return its latest rank.

Instructions

东方财富-个股人气榜-最新排名 https://guba.eastmoney.com/rank/stock?code=HK_00700 :param symbol: 带市场表示的证券代码 :type symbol: str :return: 最新排名 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo00700
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the return type (pandas.DataFrame) and the data source URL, but does not disclose additional behavioral details such as pagination, error handling, or the exact ranking criteria.

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 brief and structured, with a title, example URL, and param/return blocks. Every line adds value and it is easy to scan.

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 single-parameter read tool, the description provides the return type and a URL, but the lack of an output schema means more detail on the returned DataFrame columns would be valuable. The market scope (HK) is implied by the name and URL, not explicitly stated in the description itself.

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

Parameters3/5

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

Schema coverage is 0%, but the description compensates by explaining the symbol parameter as a 'security code with market representation' and providing the example 'HK_00700'. This adds meaning beyond the bare string type, though it lacks detail on supported market prefixes or format variations.

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 this tool retrieves the latest popularity ranking for individual stocks from East Money, with a Chinese title and example URL. It distinguishes itself from sibling tools like 'stock_hk_hot_rank_em' by specifying 'latest' and 'hk' in the name and URL.

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 explicit guidance on when to use this tool over alternatives is provided. The URL example and 'HK' hint at Hong Kong stocks, but there's no mention of exclusions or referenced sibling tools for other markets or ranking types.

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