Skip to main content
Glama
gangtiser

gangtise-mcp

by gangtiser

gangtise_income_statement_quarterly

Retrieve single-quarter income statements for A-share stocks by providing security code, fiscal year, and quarter.

Instructions

[当前日期 2026-05-27,当前年份 2026,时区 Asia/Shanghai。用户说"今天/最近/今年/当前"时按此日期换算,不要使用训练数据年份。] 查询A股单季利润表。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
securityCodeYes证券代码,如 '600519.SH'
startDateNoYYYY-MM-DD。当前日期 2026-05-27,当前年份 2026
endDateNoYYYY-MM-DD。当前日期 2026-05-27,当前年份 2026
fiscalYearNo财年列表,如 [2023, 2024]
periodNoq1 | q2 | q3 | q4 | latest
reportTypeNoconsolidated=合并 | consolidatedRestated=合并调整 | standalone=母公司 | standaloneRestated=母公司调整
fieldListNo指定返回字段
Behavior2/5

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

Annotations are absent, so the description should disclose behavioral traits. It only states 'query' without mentioning read-only nature, data source, rate limits, or any side effects. The description fails to add value beyond the basic action.

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 a single sentence with a necessary date context note. It is concise and front-loaded, but the date note could be integrated more smoothly. No wasted words.

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?

With 7 parameters, no output schema, and no annotations, the description should offer more context (e.g., available fieldList options, output format). It is minimally complete but leaves gaps for a parameter-rich tool.

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

Parameters3/5

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

Schema coverage is 100%, with all 7 parameters described in the input schema. The tool description does not add additional semantic meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 explicitly states '查询A股单季利润表' (query A-share quarterly income statement), clearly identifying the tool's verb (query), resource (income statement), and scope (A-share, quarterly). It distinguishes itself from siblings like gangtise_income_statement (likely annual) and gangtise_cash_flow_quarterly.

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 on when to use this tool versus alternatives like gangtise_income_statement (annual) or for HK stocks. The date context note is about dynamic date handling, not usage context. There are no explicit 'when to use' or 'when not to use' instructions.

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/gangtiser/gangtise-mcp'

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