Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_esg_rft_sina

Read-onlyIdempotent

Retrieve Refinitiv ESG ratings from Sina Finance's ESG rating center. Obtain structured data for analysis and decision-making.

Instructions

新浪财经-ESG评级中心-ESG评级-路孚特 https://finance.sina.com.cn/esg/grade.shtml :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, openWorldHint, idempotentHint, and destructiveHint=false. The description adds the return type (pandas.DataFrame) and the source URL, but does not disclose any further behavioral traits such as data scope, update frequency, or whether the result is a full dataset. This adds some context but remains minimal.

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 very concise, consisting of a title-like line, a URL, and return type. It is front-loaded and efficient, though the first line repeats the annotation title. It earns its place but could be more informative without becoming bloated.

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 tool with strong annotations, this is minimally adequate. It provides the source and return type but does not explain what the DataFrame contains (e.g., columns, per-stock vs aggregate data). Given the simplicity, it meets the baseline but lacks richness.

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 tool has zero parameters, so the description need not elaborate on parameter semantics. Baseline for 0 params is 4. The empty schema already provides full coverage, and the description adds nothing extra, which is appropriate.

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 tool as providing Refinitiv ESG ratings from Sina Finance's ESG Rating Center, with a direct URL and return type. This distinguishes it from sibling ESG tools like stock_esg_msci_sina and stock_esg_hz_sina. However, it lacks an explicit verb like 'get' or 'return', relying on the docstring-style format.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention other ESG rating providers, nor does it provide context on selection criteria. With multiple ESG sibling tools, this gap makes it harder for an agent to choose correctly.

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