Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_hsgt_sh_hk_spot_em

Read-onlyIdempotent

Fetch spot quotes for Hong Kong stocks traded through Shanghai-Hong Kong Stock Connect (southbound) from Eastmoney, returning structured pandas data.

Instructions

东方财富网-行情中心-沪深港通-港股通(沪>港)-股票 https://quote.eastmoney.com/center/gridlist.html#hk_sh_stocks :return: 东方财富网-行情中心-沪深港通-港股通(沪>港)-股票 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the return is a pandas.DataFrame, which is useful because there is no output schema, but it says nothing about rate limits, auth, or data freshness.

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?

It is short and front-loads the source, but the same dataset string (东方财富网-行情中心-沪深港通-港股通(沪>港)-股票) is repeated verbatim in the :return: block, and the title field duplicates it again. The URL is useful, but the duplicated naming line wastes space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter data-fetch tool, the description should at least differentiate the output from sibling HK / 港股通 spot and history tools, and clarify what the 'spot' dataset contains. It only names the source and return type, leaving the agent unable to discriminate among the many adjacent stock_hk_* and stock_hsgt_* tools.

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?

This tool takes zero parameters and schema coverage is 100%, so no parameter semantics are needed. The baseline for a no-parameter tool is 4; the description does not need to explain arguments.

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 source (东方财富网 行情中心) and the specific dataset (沪深港通-港股通(沪>港)-股票), so an agent can roughly tell it retrieves a list of stocks under the Shanghai-HK Connect southbound channel. However, it never states a verb or scope (spot quotes? full list? what columns?), and it does not distinguish itself from near-identical siblings like stock_hk_spot_em, stock_hsgt_hist_em, or stock_hk_main_board_spot_em.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative. The agent must infer applicability solely from the source label and must guess how it differs from other 港股通 / HK spot tools in the sibling list.

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

Deploy Server

Other Tools