Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_hk_main_board_spot_em

Read-onlyIdempotent

Fetches real-time quotes for Hong Kong main board stocks from East Money, enabling immediate market tracking.

Instructions

东方财富网-港股-主板-实时行情 https://quote.eastmoney.com/center/gridlist.html#hk_mainboard :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=true, idempotentHint=true, destructiveHint=false, so the safety profile is known. The description adds the return type (pandas.DataFrame) but does not mention data currency, update frequency, or any other behavioral nuance. This is adequate but minimal.

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 concise, with a clear title, a source URL, and a return type. There is no redundant or filler content, and the structure is easy to parse. Every element earns its place.

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 no-parameter spot data tool, the description is minimally sufficient but leaves gaps. It does not specify the DataFrame columns (e.g., stock code, name, latest price, change) or confirm the full scope of 'main board' coverage. Since there is no output schema, additional detail would improve completeness.

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 has zero parameters, and the input schema has 100% coverage (it is an empty object). The description adds no parameter-specific semantics, but with no parameters to clarify, the baseline of 4 is appropriate.

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 providing real-time quotes for Hong Kong Main Board stocks from Eastmoney, which is a specific verb+resource combination. It does not explicitly contrast with sibling tools, but the 'main board' scope in the name and title inherently differentiates it from tools like stock_hk_index_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 guidance on when to use this tool versus other Hong Kong stock spot tools. The description lacks any contextual hints, prerequisites, or alternative suggestions, leaving the agent to infer usage from the name alone.

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