Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

index_global_hist_sina

Read-onlyIdempotent

Access global market historical data from Sina Finance. Provide an index symbol to receive a pandas DataFrame of historical quotes for analysis.

Instructions

新浪财经-行情中心-环球市场-历史行情 https://finance.sina.com.cn/stock/globalindex/quotes/UKX :param symbol: 指数名称;可以通过 ak.index_global_name_table() 获取 :type symbol: str :return: 环球市场历史行情 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoOMX
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds the return type (pandas DataFrame) and source URL, but does not disclose potential quirks like rate limits, data granularity, or available date ranges. This is acceptable given 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.

Conciseness5/5

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

The description is compact and well-structured: title, URL, param definition, return type. Every line adds value, with no redundancy.

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 historical data tool, the description covers the purpose, parameter, and return type, but lacks details about the output DataFrame columns, date range, or usage context. With no output schema specified, more detail on the return structure would be helpful.

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 schema provides only a default value for 'symbol' with no description. The description compensates by explaining that symbol is an index name and directs to ak.index_global_name_table() to discover valid values. This is useful and goes beyond schema, though it could include examples.

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 states this provides historical market data for global indices from Sina Finance, with the resource identified by the URL and title. However, it lacks an explicit verb like 'retrieve' or 'fetch', instead using a noun phrase '环球市场历史行情'. It distinguishes from siblings via the 'sina' source in the name and URL.

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?

The description provides only a prerequisite for the symbol parameter (obtained via ak.index_global_name_table()) but does not mention when to choose this tool over alternatives like index_global_hist_em. No exclusions or alternative tool references are given.

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