Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

fund_rating_all

Read-onlyIdempotent

Retrieve the fund rating summary from East Money (天天基金网) as a structured DataFrame, enabling analysis of fund ratings across the market.

Instructions

天天基金网-基金评级-基金评级总汇 https://fund.eastmoney.com/data/fundrating.html :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?

The annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the source URL and return type, but no behavioral details such as latency, pagination, or the structure of the returned DataFrame. It does not contradict the annotations.

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 but repeats '基金评级总汇' multiple times (title, return, and rtype). It is front-loaded with the title and URL, but the repetition is unnecessary. Still, it is 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 zero-parameter, read-only tool, the description is minimally sufficient: it names the source and return type. However, it does not describe the columns or content of the DataFrame, and it doesn't clarify the scope (e.g., all funds, all rating agencies) beyond the name. Given the lack of an output schema and the presence of sibling fund rating tools, a bit more detail would help.

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 no parameters, and the schema confirms this. The description provides a return type (DataFrame), which is useful but not parameter-related. Per the baseline for 0-param tools, this scores 4.

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 is essentially a Chinese navigation path ('天天基金网-基金评级-基金评级总汇') and a URL, with a return line that repeats the tool's name. It indicates the tool returns a summary of fund ratings from Eastmoney, but it doesn't describe what a '基金评级总汇' contains or how it differs from related tools like fund_rating_ja/sh/zs. The verb is implicit ('returns'), and the resource is identifiable via the URL, so it's not entirely tautological, but little value is added beyond the name.

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 about when to use this tool vs. alternatives such as fund_rating_ja, fund_rating_sh, or fund_rating_zs. The description does not mention any exclusions, prerequisites, or preferred use cases.

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