Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_zh_index_spot_sina

Read-onlyIdempotent

Fetches real-time spot quotes for all Chinese A-share indices from Sina Finance, returning a pandas DataFrame for market monitoring and analysis.

Instructions

新浪财经-行情中心首页-A股-分类-所有指数 大量采集会被目标网站服务器封禁 IP,如果被封禁 IP,请 10 分钟后再试 https://vip.stock.finance.sina.com.cn/mkt/#hs_s :return: 所有指数的实时行情数据 :rtype: pandas.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/destructive=false, so the safety profile is covered. The description adds a genuinely useful behavioral trait beyond the annotations: heavy scraping triggers IP banning and requires a 10-minute wait. It also names the return type (pandas.DataFrame), which is helpful given no output schema.

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 purpose leads, which is good, but the body mixes a source URL, a rate-limit warning, and Sphinx-style ':return:'/':rtype:' artifacts for a trivial no-arg call. It is not bloated, but the structure is loose and some lines (URL) do not earn their place for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter spot-quote tool with no output schema, the description supplies the key facts: what it returns and the throttling risk. A brief note on scope (which indices/coverage) would make it fully complete, but nothing essential for a correct call is missing.

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 takes zero parameters, so per the rubric the baseline is 4. There is nothing parametric for the description to clarify or compensate for.

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 states the resource (新浪财经 所有指数) and the return ('所有指数的实时行情数据'), so it is clear this fetches real-time spot quotes for all A-share indices. It does not, however, differentiate itself from near-identical siblings such as stock_zh_index_spot_em or stock_hk_index_spot_sina, so an agent must infer the data-source difference.

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 statement of when to use this tool versus alternatives, nor any prerequisite or exclusion. The only operational note is a retry-after-10-minutes warning if IP-banned, which is a rate-limit caveat rather than usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools