Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_ipo_summary_cninfo

Read-onlyIdempotent

Retrieve IPO listing summary details for a given stock symbol from Cninfo, including key listing dates and company profile data.

Instructions

巨潮资讯-个股-上市相关 https://webapi.cninfo.com.cn/#/company :param symbol: 股票代码 :type symbol: str :return: 上市相关 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo600030
Behavior2/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds little beyond a source URL and return type; it does not disclose what data is included, whether it is historical or current, or any other behavioral 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 concise and follows a clear docstring structure with source, parameter, and return sections. It front-loads the source and purpose, with no redundant or verbose content, though it is under-specified in other dimensions.

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, the description needed to explain what '上市相关' includes, but it only returns a vague label. It does not specify the data fields, time range, or any distinctions from similar IPO tools, leaving the agent uncertain about the results.

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 input schema only provides a default value for symbol with 0% description coverage. The description compensates by explicitly documenting 'symbol: 股票代码' (stock code) and its string type, giving the agent the key meaning needed to invoke the tool.

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 provides '巨潮资讯-个股-上市相关' (CNInfo individual stock listing-related) and returns a pandas DataFrame, but it lacks an explicit verb and the scope '上市相关' is broad. The tool name hints at IPO summary, but the description alone does not clearly distinguish it from sibling stock_ipo_* tools.

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 given on when to use this tool versus alternatives. The many sibling IPO tools (e.g., stock_ipo_info, stock_new_ipo_cninfo) are not mentioned, nor are any prerequisites 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