Skip to main content
Glama

Ashares Sw Industries

ashares_sw_industries
Read-onlyIdempotent

Shenwan (申万) industry index board for a trading day: close, change %, turnover rate, trading amount (unit as published), share of market turnover, P/E, P/B and dividend yield for every Shenwan level-1 (31 industries), level-2 (131) or level-3 (336) industry. Answers "申万一级行业涨跌幅", "Shenwan industry PE PB", "which Shenwan industry rose most on 2026-11-06", "半导体 801081 市盈率 市净率", "SW industry valuation ranking", "行业估值". Filter to one industry with code (e.g. 801081 semiconductors, level 2) and rank with sort. Up/down stock counts, limit-up counts and 20-day highs per industry are NOT published by this source and are listed under not_provided. Source: Shenwan Hongyuan Research, SW industry index daily publication.

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-11-06",
      "sort": "change"
    },
    "name": "ashares_sw_industries"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOne 6-digit Shenwan industry code, e.g. "801080" (Electronics, L1) or "801081" (Semiconductors, L2).
dateNoTrading day, YYYY-MM-DD or YYYYMMDD (default: latest published trading day). A non-trading date returns found:false with the nearest prior trading day.
sortNoSort descending by this field (default: by code).
levelNoShenwan industry level: 1 (31 industries, default), 2 (131) or 3 (336). A code given in `code` selects its level automatically.
limitNoMax rows returned, 1-400 (default: all rows of the level).

Output Schema

NameRequiredDescriptionDefault
codeNo
dateNo
foundNo
levelNo
sourceNo
messageNo
returnedNo
sorted_byNo
data_as_ofNo
industriesNo
level_nameNo
trade_dateNo
field_notesNo
not_providedNo
industries_totalNo
valuation_for_codeNo
nearest_prior_trading_dayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the upstream source (Shenwan Hongyuan Research), that amounts use 'unit as published', and an explicit inventory of metrics the source does not publish. It does not discuss rate limits or pagination, but the output schema covers the return shape.

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 moves to usage and exclusions, so an agent can stop reading early. The long run of quoted example queries in mixed Chinese and English is slightly repetitive and could be trimmed, but each item does aid retrieval matching rather than being filler.

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?

With an output schema present and 100% parameter coverage, the description only needs to carry scope, source, and limits — and it does all three, including the not_provided list that prevents the agent from asking for unavailable data. 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.

Parameters3/5

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

Schema description coverage is 100%, so each parameter (code, date, sort, level, limit) is already fully documented in the schema, including defaults and the non-trading-day behavior. The description reinforces the intended use of `code` and `sort` but adds no syntax or constraint detail beyond what the schema states, 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 first sentence names a specific verb-scoped resource ('Shenwan industry index board for a trading day') and enumerates the exact fields returned (close, change %, turnover rate, P/E, P/B, dividend yield) plus the universe sizes (31/131/336). An agent can tell this is the Shenwan industry-index valuation board, not a generic index or sector tool, without opening the schema.

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

Usage Guidelines4/5

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

The description supplies concrete triggering queries ('申万一级行业涨跌幅', 'SW industry valuation ranking', '半导体 801081 市盈率 市净率') and explains how to narrow and rank via `code` and `sort`. It also states a boundary — up/down counts, limit-up counts and 20-day highs are not published and appear under not_provided. It stops short of naming a sibling tool to use for those missing metrics.

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.