Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

macro_china_stock_market_cap

Read-onlyIdempotent

Fetches China's national stock trading statistics from East Money, returning a pandas DataFrame with turnover, volume, and market metrics for macro analysis.

Instructions

东方财富-全国股票交易统计表 https://data.eastmoney.com/cjsj/gpjytj.html :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, and destructiveHint=false, which the description does not contradict. The description adds the return type (pandas.DataFrame) and source URL, which is useful. However, it does not disclose what columns or data range are included, so behavioral insight is limited.

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

Conciseness4/5

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

The description is short and to the point, including a source URL and return type in a structured docstring format. No extra fluff, but the inclusion of a URL and docstring markers is slightly verbose for a zero-param tool.

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?

The tool is simple (no params, no output schema), but the description does not explain what fields or statistics are included in the DataFrame. The tool name mentions 'stock_market_cap' while the description says 'trading statistics', creating potential ambiguity about the actual data content.

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, so the schema already fully covers inputs. The baseline is 4, and the description does not need to add parameter details. It correctly mentions the return type.

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 resource as '全国股票交易统计表' (national stock trading statistics) from East Money, and states the return type as pandas.DataFrame. While it omits an explicit verb like 'get' or 'list', the intent to fetch this table is clear and distinguishable from sibling macro 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?

The description provides no guidance on when to use this tool versus alternatives. It gives a source URL but no context, prerequisites, or exclusions. An agent must infer its applicability from the title 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