Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_hk_famous_spot_em

Read-onlyIdempotent

Get real-time quotes for well-known Hong Kong stocks from Eastmoney. Access current market data for famous HK companies directly.

Instructions

东方财富网-行情中心-港股市场-知名港股 https://quote.eastmoney.com/center/gridlist.html#hk_wellknown :return: 知名美股实时行情 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

Annotations already indicate read-only and idempotent. The description adds that it returns real-time quotes as a DataFrame, but it also introduces an inconsistency by calling the output US stocks. No other behavioral details (e.g., data freshness, column meanings) are disclosed. This is not an annotation contradiction, but it reduces trust.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, includes a source URL and return type, but the mislabeling of output as US stocks makes it poorly structured and confusing. The 'return' line is clearly erroneous, so the conciseness is undermined by incorrect information.

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 zero-parameter read-only tool, the description provides the source and data type, but fails to specify what columns/fields are included or clarify the market (it says HK in the heading but US in the return). Given the availability of sibling tools, it needs better differentiation and accuracy.

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 accepts no parameters, and the schema is empty (100% coverage by default). Since there are no parameters to document, the description does not need to add parameter detail; the baseline of 4 applies.

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

Purpose3/5

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

The description identifies the data source and market (港股市场, 知名港股), but the return description mislabels the result as '知名美股实时行情', conflicting with the tool's name and source URL. The core purpose is still discernible but the error undermines clarity.

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 vs sibling tools like stock_hk_spot, stock_hk_main_board_spot_em, or stock_us_famous_spot_em. The URL and market name imply it's for well-known HK stocks, but no exclusions or alternatives are provided.

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