Skip to main content
Glama
gangtiser

gangtise-mcp

by gangtiser

gangtise_balance_sheet_hk

Query Hong Kong stock balance sheets (Chinese GAAP). Filter by fiscal year, period, and report type.

Instructions

[当前日期 2026-05-27,当前年份 2026,时区 Asia/Shanghai。用户说"今天/最近/今年/当前"时按此日期换算,不要使用训练数据年份。] 查询港股资产负债表(中国会计准则),支持期间、财年、报告类型筛选。

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 | h1=中报 | q3 | h2=年报 | nsd | annual | latest
reportTypeNoconsolidated=合并 | consolidatedRestated=合并调整 | standalone=母公司 | standaloneRestated=母公司调整
fieldListNo指定返回字段
Behavior2/5

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

No annotations are provided, and the description only lists filter options. It does not disclose behavioral traits such as whether it is read-only, potential rate limits, or data freshness. The tool name suggests a query, but the description adds minimal beyond that.

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 highly concise with two sentences: one for date context and one for purpose. Every word is purposeful, and no unnecessary information is included.

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 (1 required), no output schema, and many siblings, the description adequately covers the main filtering options but omits mention of fieldList and does not guide selection among siblings. The date context instruction is useful but not about tool behavior. Overall, it is minimally complete.

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 detailed descriptions for each parameter. The description adds a summary of filter types ('期间、财年、报告类型筛选'), but does not provide additional meaning beyond what the schema already offers. Score is baseline 3 for high 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 it queries Hong Kong balance sheets under Chinese accounting standards, with specific filter options (period, fiscal year, report type). This distinguishes it from siblings like gangtise_balance_sheet (likely A-share) and other HK financial tools.

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

Usage Guidelines4/5

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

The description implies it is for HK stocks under Chinese accounting standards, but does not explicitly state when to use vs alternatives or when not to use. No sibling names are mentioned for comparison, but the scope is clear.

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