Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_cy_a_spot_em

Read-onlyIdempotent

Retrieve real-time quotes for ChiNext (创业板) stocks from East Money. Returns a pandas DataFrame of current market data.

Instructions

东方财富网-创业板-实时行情 https://quote.eastmoney.com/center/gridlist.html#gem_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, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds the data source URL and return type (pandas DataFrame), which provides useful context but does not disclose additional behavioral traits like data update frequency, potential limitations, or authentication requirements.

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 extremely concise, containing only the essential information: data source, market, return type, and a reference URL. Every line earns its place, and the key purpose is front-loaded.

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

Completeness4/5

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

Given the tool's simplicity (no parameters, no output schema), the description is fairly complete. It states what it returns (real-time quotes), the source (East Money), and the specific market (ChiNext). It could mention that it covers all ChiNext stocks, but that is implied by the board scope.

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 schema is empty. The description correctly reflects a no-parameter operation. With 0 parameters, the baseline is 4, and the description adequately avoids introducing any ambiguity.

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 the ChiNext (创业板) market from East Money, with a specific URL source. It distinguishes from sibling spot tools by naming the specific board, though it does not explicitly list alternatives.

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 regarding when to use this tool versus other similar spot tools (e.g., stock_sh_a_spot_em, stock_sz_a_spot_em). The description lacks any context about selection criteria or exclusion cases.

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