Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

bond_cov_stock_issue_cninfo

Read-onlyIdempotent

Fetch convertible bond conversion to stock data from CNINFO thematic statistics, including bond-to-equity conversion details for bond issuance reports.

Instructions

巨潮资讯-数据中心-专题统计-债券报表-债券发行-可转债转股 http://webapi.cninfo.com.cn/#/thematicStatistics :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, so safety is covered. The description adds only that it returns a pandas.DataFrame, which is useful but minimal. No additional behavioral context like pagination, data scope, or authentication needs is provided.

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

Conciseness2/5

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

The description is extremely terse, bordering on under-specification. It consists of a title-like path, a URL, and a return type label, with no complete sentence. While there is no fluff, the lack of structure or explanatory prose hurts clarity.

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?

With no output schema and no parameters, the description carries the full responsibility of explaining what data is returned. It only says '可转债转股' (convertible bond stock conversion) and 'pandas.DataFrame', without describing columns, data granularity, or any other contextual details. This is insufficient for an agent to understand the tool's output.

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?

There are zero parameters, so the description bears no burden in explaining parameter behavior. The baseline of 4 applies because with no parameters, no semantic gaps exist.

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

Purpose2/5

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

The description is essentially a navigation path ('巨潮资讯-数据中心-专题统计-债券报表-债券发行-可转债转股') with no explicit verb or action. It implies the tool returns convertible bond stock conversion data, but it reads as a label rather than a clear statement of purpose. It does not distinguish itself from sibling tools like bond_cov_issue_cninfo.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. There is no mention of preferred use cases, context, or exclusions, leaving the agent without direction to select among many similar bond issuance tools.

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