Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_financial_hk_analysis_indicator_em

Read-onlyIdempotent

Retrieve key financial indicators for Hong Kong stocks from East Money. Choose annual or report period data to analyze main metrics for any stock symbol.

Instructions

东方财富-港股-财务分析-主要指标 https://emweb.securities.eastmoney.com/PC_HKF10/NewFinancialAnalysis/index?type=web&code=00700 :param symbol: 股票代码 :type symbol: str :param indicator: choice of {"年度", "报告期"} :type indicator: str :return: 东方财富-港股-财务分析-主要指标 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo00853
indicatorNo年度
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, so the safety profile is covered. The description adds the return type (pandas.DataFrame) but does not mention any rate limits, pagination, or data freshness characteristics.

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 a compact docstring with all necessary component lines. The URL example is optional but not excessive; it does not waste words.

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 has only two simple parameters and an output schema is absent. The description specifies return type but does not enumerate which financial indicators are included, which could confuse an agent choosing among similar tools. Given the family context, more detail about the data content would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description provides full parameter documentation: symbol is the stock code and indicator is a choice of '年度' or '报告期'. This adds meaning beyond the schema's type/default definitions, enabling correct invocation.

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 retrieving Eastmoney HK stock financial analysis main indicators (东方财富-港股-财务分析-主要指标). It specifies the resource (HK stocks) and scope (main indicators), distinguishing it from A-share siblings like stock_financial_analysis_indicator.

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 on when to use this tool versus alternatives such as stock_financial_hk_report_em or stock_financial_analysis_indicator. The description only covers parameter meanings, not selection criteria.

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