FinData MCP Server

cn_ppi

Retrieve China's PPI data by month, including year-over-year, month-over-month, and cumulative changes for all industrial products and subcategories. Query by single month or date range.

Instructions

Name:
    工业生产者出厂价格指数。

Description:
    获取PPI工业生产者出厂价格指数数据。

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

Fields:
    - month: 月份(格式为YYYYMM)
    - ppi_yoy: 工业品出厂价格指数(PPI)-全部工业品-当月同比
    - ppi_mp_yoy: PPI-生产资料-当月同比
    - ppi_mp_qm_yoy: PPI-生产资料-采掘业-当月同比
    - ppi_mp_rm_yoy: PPI-生产资料-原料业-当月同比
    - ppi_mp_p_yoy: PPI-生产资料-加工业-当月同比
    - ppi_cg_yoy: PPI-生活资料-当月同比
    - ppi_cg_f_yoy: PPI-生活资料-食品类-当月同比
    - ppi_cg_c_yoy: PPI-生活资料-衣着类-当月同比
    - ppi_cg_adu_yoy: PPI-生活资料-一般日用品类-当月同比
    - ppi_cg_dcg_yoy: PPI-生活资料-耐用消费品类-当月同比

    - ppi_mom: PPI-全部工业品-环比
    - ppi_mp_mom: PPI-生产资料-环比
    - ppi_mp_qm_mom: PPI-生产资料-采掘业-环比
    - ppi_mp_rm_mom: PPI-生产资料-原料业-环比
    - ppi_mp_p_mom: PPI-生产资料-加工业-环比
    - ppi_cg_mom: PPI-生活资料-环比
    - ppi_cg_f_mom: PPI-生活资料-食品类-环比
    - ppi_cg_c_mom: PPI-生活资料-衣着类-环比
    - ppi_cg_adu_mom: PPI-生活资料-一般日用品类-环比
    - ppi_cg_dcg_mom: PPI-生活资料-耐用消费品类-环比

    - ppi_accu: PPI-全部工业品-累计同比
    - ppi_mp_accu: PPI-生产资料-累计同比
    - ppi_mp_qm_accu: PPI-生产资料-采掘业-累计同比
    - ppi_mp_rm_accu: PPI-生产资料-原料业-累计同比
    - ppi_mp_p_accu: PPI-生产资料-加工业-累计同比
    - ppi_cg_accu: PPI-生活资料-累计同比
    - ppi_cg_f_accu: PPI-生活资料-食品类-累计同比
    - ppi_cg_c_accu: PPI-生活资料-衣着类-累计同比
    - ppi_cg_adu_accu: PPI-生活资料-一般日用品类-累计同比
    - ppi_cg_dcg_accu: PPI-生活资料-耐用消费品类-累计同比

Input Schema

TableJSON Schema

Name	Required	Description	Default
`m`	No
`start_m`	No
`end_m`	No
`fields`	No

Tool Definition Quality

B3.1/5.0

Behavior2/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 does not disclose whether the operation is read-only, whether authentication is needed, rate limits, or any side effects. The minimal description '获取...数据' implies a safe read, but this is not explicit.

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 a name, description, args table, and fields list. It is front-loaded with purpose. The fields list is lengthy but necessary. No unnecessary 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 that there is no output schema, the description partially covers what data is returned via the fields list. However, it lacks details on response format, pagination, error handling, and default behavior when parameters are omitted.

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 input schema has 0% description coverage, but the tool description provides a detailed table explaining each parameter's format and purpose. It also lists the available field values. This adds significant meaning beyond the schema's bare titles.

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 explicitly states the tool retrieves PPI producer price index data ('获取PPI工业生产者出厂价格指数数据'). The name and description are clear. However, it does not differentiate from sibling tools like cn_cpi or cn_gdp, but the specificity of PPI makes confusion unlikely.

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?

No guidance is provided on when to use this tool compared to alternatives. The description does not mention prerequisites, exclusions, or when to prefer other tools. The parameter descriptions are present but usage context is missing.

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

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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