Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

index_stock_cons_weight_csindex

Read-onlyIdempotent

Retrieves current constituent stock weights for a given Chinese stock index from the official CSI website. Returns a pandas DataFrame of index components and their weightings.

Instructions

中证指数网站-样本权重 https://www.csindex.com.cn/zh-CN/indices/index-detail/000300 :param symbol: 指数代码, 可以通过 ak.index_stock_info() 接口获取 :type symbol: str :return: 最新指数的成份股权重 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo000300
Behavior3/5

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

Annotations already declare safe read-only, idempotent behavior. The description adds that it returns the latest weights only, not historical data, and specifies the data source. However, it does not disclose any rate limits, error cases, or additional side effects, though these are less critical given the annotations.

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 compact, with a title, URL, and docstring-style param and return sections. Each part is useful, though the URL and title are slightly redundant with the parameter default. Overall, it is front-loaded and free of fluff.

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?

For a simple one-parameter tool with no output schema, the description explains the return type (pandas DataFrame) and content (constituent weights), and that it is the latest data. It could specify columns or sorting, but the core usage context is sufficiently covered.

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 schema only provides type and default for symbol. The description enriches this by explaining symbol is an index code and pointing users to ak.index_stock_info() for valid values, which goes beyond the bare schema and helps correctly invoke the tool.

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 the tool returns the latest constituent stock weights for CSI indices, with a specific source URL. It distinguishes itself from sibling tools like index_stock_cons_csindex (which likely returns constituent lists) by focusing on weights.

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 only mentions how to obtain the symbol via ak.index_stock_info(), but does not explain trade-offs with sibling tools like index_stock_cons_sina or index_stock_cons.

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