Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf

stock_us_spot

Read-onlyIdempotent

Fetch all U.S. stock market spot quotes with a 15-minute delay. Use it to retrieve current prices and market data for every US-listed stock via AKShare.

Instructions

新浪财经-所有美股的数据,注意延迟 15 分钟 https://finance.sina.com.cn/stock/usstock/sector.shtml :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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new context not present in the annotations: a 15-minute data delay and the return type (pandas.DataFrame), which materially affects how an agent should interpret freshness.

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 definition is short and the important caveat (15-minute delay) is front-loaded. The embedded source URL is arguably noise, but it is compact and the rest is efficiently worded.

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?

With no parameters and no output schema, the description supplies what an agent needs: the resource, the source, the freshness limitation, and the return type. Only tool-selection context relative to its many siblings 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 the baseline is 4. There are no arguments whose semantics could be clarified or missed.

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 a specific verb-like capability (returning quotes for all US stocks) and names the data source (Sina Finance). It clarifies scope as the entire US market spot snapshot, but does not distinguish itself from nearby siblings such as stock_us_spot_em, stock_us_famous_spot_em, or stock_us_daily.

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 like stock_us_spot_em or stock_us_daily. The only usage-relevant hint is the 15-minute delay caveat, which informs expectations rather than tool selection.

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