Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_zh_a_spot_em

Read-onlyIdempotent

Fetch real-time quotes for Shanghai, Shenzhen, and Beijing A-shares from East Money, returned as a pandas DataFrame.

Instructions

东方财富网-沪深京 A 股-实时行情 https://quote.eastmoney.com/center/gridlist.html#hs_a_board :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, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the source URL and confirms the return type as pandas.DataFrame, but does not disclose potential rate limits or data freshness, which is acceptable for a read-only spot quote tool.

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 compact, with a title, source URL, and return type in three short lines. Every element adds information; the URL is useful for source verification.

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

Completeness5/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 with strong annotations, the description provides the essential behavior: returns real-time quotes for all A-shares from Eastmoney as a DataFrame. No output schema exists, but the tool's simplicity and the description's clarity keep it complete.

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 input schema has zero parameters, so schema description coverage is trivially 100%. The description correctly adds no parameter information, and the baseline for zero-param tools is 4.

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 that the tool returns real-time A-share quotes from Eastmoney, covering Shanghai, Shenzhen, and Beijing. The name 'stock_zh_a_spot_em' and the title '东方财富网-沪深京 A 股-实时行情' explicitly distinguish it from exchange-specific or alternate-source sibling tools.

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 guidance is provided on when to use this tool versus alternatives such as stock_sh_a_spot_em or stock_zh_a_spot. The description only states what the tool does, without describing usage context or exclusions.

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