Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

fund_rating_ja

Read-onlyIdempotent

Retrieve fund ratings from Tiantian Fund Network's Jiu'an Jinxin rating for a specified date. Get structured data for investment analysis.

Instructions

天天基金网-基金评级-济安金信评级 https://fund.eastmoney.com/data/fundrating_4.html :param date: 日期; https://fund.eastmoney.com/data/fundrating_4.html 获取查询日期 :type date: str :return: 济安金信评级 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo20230331
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, covering the safety profile. The description adds the return type (pandas.DataFrame) and source URL, but no additional behavioral traits such as pagination, rate limits, or error handling.

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 short and structured with param/return tags, making it easy to parse. However, the source URL is repeated twice, and the text is somewhat terse without a clear top-level purpose statement.

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?

The tool is simple with one parameter, but no output schema exists. The description does not specify the date format, nor does it describe the columns or content of the returned DataFrame. Given the absence of an output schema, this is a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter 'date' at 0% description coverage. The description calls it '日期' (date) and points to a URL for obtaining the query date, but does not specify the expected format (e.g., YYYYMMDD) or valid values beyond the default '20230331' in the schema.

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 '天天基金网-基金评级-济安金信评级' (Eastmoney Fund Network - Fund Rating - Ji'an Jinxin Rating) and indicates the return type as Ji'an Jinxin Rating. It identifies the specific rating system and source, but lacks a strong verb and does not explicitly differentiate from sibling tools like fund_rating_sh or fund_rating_zs.

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 when-to-use or alternative guidance is provided. The description only covers the parameter and return type, without explaining when to choose this over other fund_rating_* tools or any context about the rating system.

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