Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

bond_index_general_cbond

Read-onlyIdempotent

Fetches ChinaBond index data for a given index category, indicator (price, yield, duration, convexity), and maturity period, returning structured time series for analysis.

Instructions

中国债券信息网-中债指数-中债指数族系 https://yield.chinabond.com.cn/cbweb-mn/indices/singleIndexQueryResult :param index_category: see result of available_bond_index() :type index_category: str :param indicator: choice of {"全价", "净价", "财富", "平均市值法久期", "平均现金流法久期", "平均市值法凸性", "平均现金流法凸性", "平均现金流法到期收益率", "平均市值法到期收益率", "平均基点价值", "平均待偿期", "平均派息率", "指数上日总市值", "财富指数涨跌幅", "全价指数涨跌幅", "净价指数涨跌幅", "现券结算量"} :type indicator: str :param period: choice of {"总值", "1年以下", "1-3年", "3-5年", "5-7年", "7-10年", "10年以上", "0-3个月", "3-6个月", "6-9个月", "9-12个月", "0-6个月", "6-12个月"} :type period: str :return: 指定指数的指定指标的指定期限分段数据 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNo总值
indicatorNo全价
index_categoryNo新综合指数
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no behavioral context beyond the annotations—no mention of web fetching, rate limits, authentication, or potential failure modes. It does not contradict annotations, but also provides no additional transparency.

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 a docstring with :param: and :return: sections, which is reasonably structured but not front-loaded with a high-level summary. It includes useful parameter choices and the URL but is somewhat verbose for a tool description.

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?

With no output schema, the description provides the return type and the general meaning. It covers parameter choices and references the index list tool, but lacks context on data shape, date handling, error behavior, and differentiation from sibling bond index tools, making it only minimally complete.

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 has no descriptions or enums (coverage 0%), but the description lists all allowed values for indicator and period, and references available_bond_index() for index_category. This adds essential meaning beyond the schema, though it does not explain the semantics of each choice.

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 states it returns '指定指数的指定指标的指定期限分段数据' (segment data for a specified index, indicator, and period) from the China Bond Index family (中债指数族系). This is a clear purpose, but it does not differentiate from sibling tools like bond_composite_index_cbond or bond_new_composite_index_cbond, so it lacks sibling distinction.

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?

There is no guidance on when to use this tool versus other bond index tools. The only hint is a reference to available_bond_index() for index_category, but no explicit comparisons or exclusions are provided.

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