Skip to main content
Glama

Cn Index Valuation

cn_index_valuation
Read-onlyIdempotent

Index VALUATION for a China Securities Index Co. (CSI) or SSE index code: the latest trading day's P/E and dividend yield plus roughly the last 20 trading days, dated. Answers "CSI Dividend Index 000922 latest P/E and dividend yield", "SSE Dividend 000015 valuation", "H30269 dividend low volatility index P/E", "930955 红利低波100 市盈率 股息率", "中证红利指数估值". Returns four published figures per day: P/E1 (total shares), P/E2 (calculation shares), D/P1 (dividend yield on total shares, %) and D/P2 (dividend yield on calculation shares, %). NOT in this source, and never estimated: P/B (市净率) and valuation percentile / history rank (估值分位) -- the response lists them under not_provided. Code is case-sensitive upstream: numeric codes as 6 digits (000922, 000300, 930955), letter-prefixed ones with an upper-case letter (H30269). An unknown or unpublished code returns found:false. Source: China Securities Index Co., daily index indicators.

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": {
      "index_code": "000922"
    },
    "name": "cn_index_valuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many trading days of history to return, 1-30 (default: everything published, about 20).
index_codeYesCSI/SSE index code, e.g. "000922" (CSI Dividend), "000015" (SSE Dividend), "H30269" (CSI Dividend Low Volatility), "930955" (CSI Dividend Low Volatility 100), "000300" (CSI 300).

Output Schema

NameRequiredDescriptionDefault
foundNo
latestNo
sourceNo
historyNo
messageNo
data_as_ofNo
index_codeNo
trade_dateNo
field_notesNo
not_providedNo
index_name_cnNo
index_name_enNo
history_trading_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world. The description adds behavior the annotations cannot: upstream code handling is case-sensitive (6-digit numerics, upper-case letter prefix such as H30269), and an unknown or unpublished code returns found:false rather than erroring or guessing. It also names the upstream source (China Securities Index Co. daily index indicators), which bounds 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?

Front-loaded with purpose and output figures, then exclusions, then code-format caveats, then source — a sensible order with no filler. It is on the long side because of five stacked example queries, which is the only element that could be trimmed without losing semantics.

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?

Covers everything an agent needs before calling: what the four returned figures mean, the lookback covered, what is deliberately absent, the code-format pitfall, and the not-found response. With an output schema present, it correctly does not re-document the response envelope.

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?

Schema coverage is 100%, so baseline is 3. The description still adds real value beyond the schema: the code-format rules (numeric vs. upper-case letter prefix, case-sensitivity upstream) explain a failure mode the schema examples alone don't warn about, and it confirms that 'days' means trading days of history. That is meaning beyond the structured fields.

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?

States a specific verb+resource ('Index VALUATION for a CSI or SSE index code') and enumerates exactly what comes back: P/E1, P/E2, D/P1, D/P2 for the latest day plus ~20 trading days. Its domain (index fundamentals) is clearly distinct from every sibling tool listed, none of which touch index valuation.

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?

Gives concrete user-question phrasings (English and Chinese) that should route here, and explicit exclusions: P/B and valuation percentile are 'NOT in this source, and never estimated', with the response flagging them under not_provided. It doesn't name a sibling to use instead for those figures, but no sibling covers them, so the exclusion itself is the useful guidance.

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.