Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_rank_forecast_cninfo

Read-onlyIdempotent

Retrieve investment rating forecasts from CNINFO for a given date. Access analyst ratings for stocks to inform investment decisions.

Instructions

巨潮资讯-数据中心-评级预测-投资评级 https://webapi.cninfo.com.cn/#/thematicStatistics?name=%E6%8A%95%E8%B5%84%E8%AF%84%E7%BA%A7 :param date: 查询日期 :type date: str :return: 投资评级 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo20230817
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds the return type (pandas.DataFrame) and source URL, but does not disclose any additional behavioral traits such as data scope, pagination, or limitations.

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 uses a docstring structure with title, URL, parameter, and return sections. It includes the title redundantly and a long URL, but overall remains compact and easy to scan.

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?

For a simple one-parameter read-only tool, the description covers the basics: what it returns and the parameter meaning. However, it lacks detail on the contents of the returned DataFrame (e.g., columns, scope), and provides no comparison with similar rating tools, leaving some ambiguity for an agent.

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 description defines 'date' as the query date (查询日期) and specifies its type as str, adding meaning beyond the bare schema. It does not explicitly state the date format, but the schema default '20230817' implies YYYYMMDD.

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 clearly identifies the resource as investment ratings (投资评级) from CNInfo, and the return type is specified as a pandas DataFrame. However, it lacks an explicit action verb like 'fetch' or 'retrieve', and does not distinguish itself from other rating-related tools in the sibling list.

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 alternatives. The description only includes parameter documentation and a source URL, with no context about use cases 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