Skip to main content
Glama

China Exchange Data

Ashares Market Bars

ashares_market_bars
Read-onlyIdempotent

沪市全市场行情, Full-market latest-session board snapshot for SSE-listed A-shares (~2,358 stocks): code, name, last price, change %, volume, turnover amount (成交额). Built for running screens (momentum vs index, top movers) without querying each stock individually. This is the LATEST available trading session only (a live board snapshot, not a historical-date archive), SZSE does not expose an equivalent single-call full-market bulk endpoint (its per-stock snapshot report needs one call per code), so this tool covers the Shanghai exchange only; asking for a past date returns the latest session with a note rather than silently substituting data. Answers 'A股全市场行情', 'SSE full board today', 'screen all Shanghai A-shares by turnover'. Source: SSE yunhq public quote list (keyless).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2026-09-05",
      "limit": 15
    },
    "name": "ashares_market_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoRequested date, YYYY-MM-DD. Informational only, the tool always returns the latest available SSE session and reports whether it matches this date.
sortNoSort rows by turnover amount (default), change %, or volume, descending.
limitNoMax rows to return, 1-2500 (default 500). The response always reports the true total row count on the board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Requested date, YYYY-MM-DD. Informational only — the tool always returns the latest available SSE session and reports whether it matches this date."New value: +"Requested date, YYYY-MM-DD. Informational only, the tool always returns the latest available SSE session and reports whether it matches this date."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description's burden is lower, yet it still adds real behavioral context: latest-session-only semantics, non-silent handling of a mismatched date, keyless public source, and the fact that the response reports the true total row count. It stops short of describing error behavior or rate limits, but the safety and mutation profile is fully consistent with 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.

Conciseness4/5

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

The definition is front-loaded with the resource and field list, then the usage and scope caveats, which is the right order for an agent. It is dense but slightly overlong: the repeated emphasis on 'latest session only' appears twice, and the quoted query-phrase list is a minor luxury rather than essential information.

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

Completeness5/5

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

For a three-parameter, zero-required read tool with no output schema, the description covers everything an agent needs: scope of the market, freshness semantics, what a date parameter does and does not do, sort/limit behavior, and where the data comes from. Nothing required for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters (date, sort, limit) are already documented in the input schema, including enum values and the limit range. The description reinforces the snapshot semantics and the total-count reporting but adds no syntax or format detail beyond what the schema already carries, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource immediately: a full-market latest-session board snapshot for SSE-listed A-shares (~2,358 stocks), then enumerates the returned fields (code, name, last price, change %, volume, turnover amount). It also scopes the tool against siblings by restricting it to SSE and pointing out that SZSE has no equivalent single-call bulk endpoint.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the intended jobs ('running screens', 'momentum vs index, top movers') and the alternative it replaces (querying each stock individually). It also states the exclusion clearly: this is latest-session only, and requesting a past date returns the latest session with a note rather than silently substituting data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.