Skip to main content
Glama
zlinzzzz

FinData MCP Server

by zlinzzzz

sf_month

Retrieve monthly social financing data including increments and stock values. Query by single month, multiple months, or a date range.

Instructions

Name:
    社融数据(月度)。

Description:
    获取月度社会融资数据。

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

Fields:
    - month: 月度
    - inc_month: 社融增量当月值(亿元)
    - inc_cumval: 社融增量累计值(亿元)
    - stk_endval: 社融存量期末值(万亿元)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mNo
start_mNo
end_mNo
fieldsNo
Behavior2/5

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

No annotations are provided, and the description does not disclose behavior beyond the basic retrieval. It lacks details on authentication, rate limits, default behavior when parameters are omitted, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, uses a clear table for parameters, and lists fields in bullet points. No redundant content, and the structure is easy to parse.

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

Completeness4/5

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

The description adequately covers the 4 optional parameters and lists available fields, but lacks explanation of default return behavior when no parameters are specified. No output schema, but field list helps. It is fairly complete for a simple retrieval tool.

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?

With 0% schema description coverage, the description compensates well by explaining parameter formats (YYYYMM), usage constraints (start_m/end_m paired), and field selection from a predefined list. This adds significant meaning beyond the raw schema.

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 the tool retrieves monthly social financing data. The name 'sf_month' and description '获取月度社会融资数据' directly convey the purpose, and it is distinct from sibling tools like cn_cpi or cn_gdp.

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 provides parameter usage details (e.g., multiple months, start_m/end_m pairing) but does not offer guidance on when to use this tool over siblings. No explicit context for selection.

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