Skip to main content
Glama
zlinzzzz

FinData MCP Server

by zlinzzzz

cn_gdp

Retrieve China's quarterly GDP data, including cumulative values and year-over-year growth rates for overall economy and primary, secondary, and tertiary industries. Filter by specific quarters or date range.

Instructions

Name:
    GDP数据。

Description:
    获取国民经济之GDP数据。

Args:
    | 名称       | 类型  | 必填 | 描述                                   |
    |------------|-------|------|----------------------------------------|
    | q | str   | 否    | 季度(2019Q1表示,2019年第一季度),支持多个季度同时输入,逗号分隔 |
    | start_q | str   | 否    | 开始季度(2019Q1表示,2019年第一季度),与end_q同时使用 |
    | end_q   | str   | 否    | 结束季度(2019Q1表示,2019年第一季度),与start_q同时使用  |
    | fields     | list  | 否    | 从Fields中选取需要查询的字段  |

Fields:
    - quarter: 季度
    - gdp: GDP累计值(亿元)
    - gdp_yoy: 当季同比增速(%)
    - pi: 第一产业累计值(亿元)
    - pi_yoy: 第一产业同比增速(%)
    - si: 第二产业累计值(亿元)
    - si_yoy: 第二产业同比增速(%)
    - ti: 第三产业累计值(亿元)
    - ti_yoy: 第三产业同比增速(%)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
start_qNo
end_qNo
fieldsNo
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention whether the tool is read-only, if it requires authentication, or any side effects. The name and description imply it is a query, 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 clear sections (Name, Description, Args, Fields). It is concise yet informative, though the main description is only one sentence and could be expanded slightly to improve completeness.

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?

The description adequately covers parameter usage but lacks details on output format (e.g., whether results are a list or single object) and behavior when no parameters are provided (e.g., returns all data). No output schema exists, so the description should fill this gap.

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 includes a detailed Args table explaining each parameter: 'q' format (e.g., 2019Q1) and support for multiple quarters, 'start_q' and 'end_q' for range queries, and 'fields' as a list of field names. It also specifies valid field names in a separate Fields section, adding significant value beyond the schema (which has 0% description coverage).

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 states '获取国民经济之GDP数据' (Get GDP data of national economy), specifying the verb 'get' and the resource 'GDP data'. This distinguishes it from sibling tools that cover other economic indicators like CPI, PMI, etc.

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?

The description provides no guidance on when to use this tool versus alternatives. No mention of prerequisites, typical use cases, or scenarios where other tools would be more appropriate.

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