Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_esg_msci_sina

Read-onlyIdempotent

Fetch MSCI ESG ratings from Sina Finance's ESG rating center and get them as a pandas DataFrame for financial analysis.

Instructions

新浪财经-ESG评级中心-ESG评级-MSCI https://finance.sina.com.cn/esg/grade.shtml :return: MSCI :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=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat those. It adds the source URL and the fact that the return type is a pandas DataFrame. However, it discloses no additional behaviors such as rate limits, refresh frequency, or special fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and front-loaded with the title and URL, but it is more of a header than an explanatory description. It is concise but lacks structured elaboration, and the return type is given in a docstring-like format rather than a natural sentence.

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?

For a zero-parameter data retrieval tool with no output schema, the description should clearly state what the resulting DataFrame contains. Merely saying 'MSCI' is ambiguous—does it return all MSCI ratings? For which companies? Any history? The source URL helps but does not replace a clear explanation of the returned data.

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, and the schema is empty, so the description is not required to explain parameters. Baseline for zero-parameter tools is 4. The description does not contradict 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 identifies the tool as Sina Finance ESG Rating Center's MSCI rating, but its purpose is stated via a title-like phrase rather than a clear verb-driven explanation. The name itself already conveys the same information, making the description only slightly more explanatory. It does specify the source and the return type, which adds a little clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 vs. alternative ESG tools. The description does not mention any context, prerequisites, or exclusions. Even with sibling tools like stock_esg_hz_sina or stock_esg_rate_sina, no differentiation is provided.

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