Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_financial_abstract

Read-onlyIdempotent

Fetch key financial metrics for any Chinese A-share stock from Sina Finance. Provide a stock symbol to get summarized financial statements and key indicators.

Instructions

新浪财经-财务报表-关键指标 https://vip.stock.finance.sina.com.cn/corp/go.php/vFD_FinanceSummary/stockid/600004.phtml :param symbol: 股票代码 :type symbol: str :return: 新浪财经-财务报表-关键指标 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo600004
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already indicate a safe read-only, idempotent operation. The description adds minimal behavioral context by specifying the return type (pandas.DataFrame) and the example URL, but does not disclose details about data coverage, potential failures, or any side effects beyond what annotations imply.

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

Conciseness3/5

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

The description is reasonably concise but repeats the same Chinese title twice ('新浪财经-财务报表-关键指标') and includes a URL that, while informative, is not essential. The docstring-like structure is clear but could be more streamlined.

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

Completeness2/5

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

The tool has no output schema, yet the description only states that a pandas.DataFrame is returned. It does not specify what key indicators are included, the time period, or how it differs from similar financial analysis tools, leaving an agent under-informed for precise invocation.

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

Parameters3/5

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

The only parameter 'symbol' is described as a stock code with a default value in the schema. The description adds minimal clarification by explicitly labeling it '股票代码' (stock code), but this is largely self-evident from the parameter name and default example in the URL.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool returns Sina Finance financial statement key indicators, with a URL and DataFrame return type. However, it lacks a clear verb (e.g., 'get' or 'fetch') and does not distinguish it from closely related sibling tools such as stock_financial_abstract_ths or 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 is provided on when to use this tool versus the many available alternatives. The description only documents the symbol parameter and return type, without mentioning appropriate contexts 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