Skip to main content
Glama
zlinzzzz

FinData MCP Server

by zlinzzzz

cn_cpi

Retrieve China's CPI data including national, urban, and rural consumer price indices. Filter by month or date range, and select fields such as month-over-month and year-over-year changes.

Instructions

Name:
    居民消费价格指数。

Description:
    获取CPI居民消费价格数据,包括全国、城市和农村的数据。

Args:
    | 名称       | 类型  | 必填 | 描述                                   |
    |------------|-------|------|----------------------------------------|
    | m | str   | 否    | 月份(YYYYMM),支持多个月份同时输入,逗号分隔 |
    | start_m | str   | 否    | 开始月份(YYYYMM),与end_m同时使用 |
    | end_m   | str   | 否    | 结束月份(YYYYMM),与start_m同时使用  |
    | fields     | list  | 否    | 从Fields中选取需要查询的字段  |

Fields:
    - month: 月份
    - nt_val: 全国当月值
    - nt_yoy: 全国同比(%)
    - nt_mom: 全国环比(%)
    - nt_accu: 全国累计值
    - town_val: 城市当月值
    - town_yoy: 城市同比(%)
    - town_mom: 城市环比(%)
    - town_accu: 城市累计值
    - cnt_val: 农村当月值
    - cnt_yoy: 农村同比(%)
    - cnt_mom: 农村环比(%)
    - cnt_accu: 农村累计值

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mNo
start_mNo
end_mNo
fieldsNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the tool as retrieving data (read operation) but does not explicitly state it is read-only, idempotent, or safe. No mention of rate limits, error behavior, or side effects. Adequate but minimal.

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 description is well-structured with sections (Name, Description, Args, Fields). It is reasonably concise for the information provided, though the table could be slightly more compact. No wasted sentences.

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

Completeness3/5

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

Given the lack of output schema, the description helpfully lists the fields. It covers all arguments and their usage. However, it lacks examples, error handling details, or explanation of the output format (e.g., JSON structure). Adequate for simple data retrieval but could be more complete.

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

Parameters5/5

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

The description provides a detailed table for each parameter (m, start_m, end_m, fields) with format and usage, plus lists all possible field values. This adds significant meaning beyond the schema, which lacks descriptions. Schema coverage is 0%, so the description compensates fully.

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 clearly specifies that the tool retrieves CPI (Consumer Price Index) data, including national, urban, and rural datasets. This distinguishes it from sibling tools like cn_gdp or cn_pmi, which focus on other economic indicators.

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

Usage Guidelines3/5

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

The description explains how to use the parameters (m, start_m, end_m, fields) but does not explicitly state when to use this tool versus alternatives. It does not provide exclusions or guidance on choosing this tool over siblings, leaving the context implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zlinzzzz/finData-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server