Skip to main content
Glama
guangxiangdebizi

FinanceMCP

company_performance_hk

Retrieve comprehensive financial data for Hong Kong-listed companies, including income statements, balance sheets, and cash flow statements, by specifying stock codes, date ranges, and report types.

Instructions

获取港股上市公司综合表现数据,包括利润表、资产负债表、现金流量表等财务报表数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
data_typeYes数据类型:income(利润表)、balance(资产负债表)、cashflow(现金流量表)
end_dateYes结束日期,格式为YYYYMMDD,如'20231231'
ind_nameNo指定财务科目名称,如'营业额'、'毛利'、'除税后溢利'等,不指定则返回全部科目
periodNo特定报告期,格式为YYYYMMDD,如'20231231'表示2023年年报。指定此参数时将忽略start_date和end_date
start_dateYes起始日期,格式为YYYYMMDD,如'20230101'
ts_codeYes港股代码,如'00700.HK'表示腾讯控股,'00939.HK'表示建设银行

Implementation Reference

  • Core handler function for the 'company_performance_hk' tool. Processes input parameters, selects appropriate Tushare API endpoint based on data_type (income, balance, cashflow), fetches data using fetchHkFinancialData helper, applies formatting, and returns structured content or error.
    async run(args: { 
      ts_code: string; 
      data_type: string; 
      start_date: string;
      end_date: string;
      period?: string;
      ind_name?: string;
    }) {
      try {
        console.log('港股公司综合表现查询参数:', args);
        
        const TUSHARE_API_KEY = TUSHARE_CONFIG.API_TOKEN;
        const TUSHARE_API_URL = TUSHARE_CONFIG.API_URL;
        
        if (!TUSHARE_API_KEY) {
          throw new Error('请配置TUSHARE_TOKEN环境变量');
        }
    
        // 根据data_type选择对应的接口
        let apiInterface = '';
        let formatFunction: any = null;
        
        switch (args.data_type) {
          case 'income':
            apiInterface = 'hk_income';
            formatFunction = formatHkIncomeData;
            break;
          case 'balance':
            apiInterface = 'hk_balancesheet';
            formatFunction = formatHkBalanceData;
            break;
          case 'cashflow':
            apiInterface = 'hk_cashflow';
            formatFunction = formatHkCashflowData;
            break;
          default:
            throw new Error(`不支持的数据类型: ${args.data_type}`);
        }
    
        const result = await fetchHkFinancialData(
          apiInterface,
          args.ts_code,
          args.period,
          args.start_date,
          args.end_date,
          args.ind_name,
          TUSHARE_API_KEY,
          TUSHARE_API_URL
        );
    
        if (!result.data || result.data.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: `# ${args.ts_code} 港股${getDataTypeName(args.data_type)}数据\n\n❌ 未找到相关数据,请检查股票代码或日期范围`
              }
            ]
          };
        }
    
        // 使用对应的格式化函数
        if (formatFunction) {
          const formattedResult = formatFunction(result.data, args.ts_code, args.data_type);
          return formattedResult;
        } else {
          // 如果没有实现格式化器,返回原始数据
          return {
            content: [
              {
                type: "text",
                text: `# ${args.ts_code} 港股${getDataTypeName(args.data_type)}数据\n\n⚠️ 格式化器待实现,以下为原始数据:\n\n${JSON.stringify(result.data, null, 2)}`
              }
            ]
          };
        }
    
      } catch (error) {
        console.error('港股公司业绩查询错误:', error);
        return {
          content: [
            {
              type: "text",
              text: `❌ 港股公司业绩查询失败: ${error instanceof Error ? error.message : String(error)}`
            }
          ],
          isError: true
        };
      }
    }
  • Input schema definition for the tool, including parameters for HK stock code, data type (income/balance/cashflow), date ranges, optional period and specific indicator name.
    name: "company_performance_hk",
    description: "获取港股上市公司综合表现数据,包括利润表、资产负债表、现金流量表等财务报表数据",
    parameters: {
      type: "object",
      properties: {
        ts_code: {
          type: "string",
          description: "港股代码,如'00700.HK'表示腾讯控股,'00939.HK'表示建设银行"
        },
        data_type: {
          type: "string",
          description: "数据类型:income(利润表)、balance(资产负债表)、cashflow(现金流量表)",
          enum: ["income", "balance", "cashflow"]
        },
        start_date: {
          type: "string",
          description: "起始日期,格式为YYYYMMDD,如'20230101'"
        },
        end_date: {
          type: "string",
          description: "结束日期,格式为YYYYMMDD,如'20231231'"
        },
        period: {
          type: "string",
          description: "特定报告期,格式为YYYYMMDD,如'20231231'表示2023年年报。指定此参数时将忽略start_date和end_date"
        },
        ind_name: {
          type: "string",
          description: "指定财务科目名称,如'营业额'、'毛利'、'除税后溢利'等,不指定则返回全部科目"
        }
      },
      required: ["ts_code", "data_type", "start_date", "end_date"]
    },
  • src/index.ts:328-336 (registration)
    Tool registration in the stdio MCP server's CallToolRequestSchema handler. Extracts arguments and calls the tool's run method.
    case "company_performance_hk": {
      const ts_code = String(request.params.arguments?.ts_code);
      const data_type = String(request.params.arguments?.data_type);
      const start_date = String(request.params.arguments?.start_date);
      const end_date = String(request.params.arguments?.end_date);
      const period = request.params.arguments?.period ? String(request.params.arguments.period) : undefined;
      const ind_name = request.params.arguments?.ind_name ? String(request.params.arguments.ind_name) : undefined;
      return await companyPerformance_hk.run({ ts_code, data_type, start_date, end_date, period, ind_name });
    }
  • Tool registration in the HTTP MCP server's tools/call handler switch statement.
    case 'company_performance_hk':
      return await companyPerformance_hk.run({
        ts_code: String(args?.ts_code),
        data_type: String(args?.data_type),
        start_date: String(args?.start_date),
        end_date: String(args?.end_date),
        period: args?.period ? String(args.period) : undefined,
        ind_name: args?.ind_name ? String(args.ind_name) : undefined,
      });
  • Helper function that constructs and sends POST request to Tushare API for HK financial data, parses the response from array format to object array.
    async function fetchHkFinancialData(
      apiInterface: string,
      ts_code: string,
      period?: string,
      start_date?: string,
      end_date?: string,
      ind_name?: string,
      apiKey?: string,
      apiUrl?: string
    ): Promise<any> {
      const requestData: any = {
        api_name: apiInterface,
        token: apiKey,
        params: {
          ts_code: ts_code
        }
      };
    
      // 根据是否指定period来设置参数
      if (period) {
        requestData.params.period = period;
      } else if (start_date && end_date) {
        requestData.params.start_date = start_date;
        requestData.params.end_date = end_date;
      }
    
      // 如果指定了具体的财务科目
      if (ind_name) {
        requestData.params.ind_name = ind_name;
      }
    
      const response = await fetch(apiUrl!, {
        method: 'POST',
        headers: {
          'Content-Type': 'application/json'
        },
        body: JSON.stringify(requestData),
        signal: AbortSignal.timeout(TUSHARE_CONFIG.TIMEOUT)
      });
    
      if (!response.ok) {
        throw new Error(`Tushare API请求失败: ${response.status} ${response.statusText}`);
      }
    
      const data = await response.json();
      
      if (data.code !== 0) {
        throw new Error(`Tushare API错误: ${data.msg || '未知错误'}`);
      }
    
      // 将返回的数组格式转换为对象数组
      const items: any[] = [];
      if (data.data && data.data.items && data.data.items.length > 0) {
        const fields = data.data.fields;
        for (const item of data.data.items) {
          const obj: any = {};
          fields.forEach((field: string, index: number) => {
            obj[field] = item[index];
          });
          items.push(obj);
        }
      }
    
      return { data: items };
    } 
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 of behavioral disclosure. It states the tool retrieves data ('获取'), implying a read-only operation, but doesn't clarify permissions, rate limits, data freshness, or error handling. For a financial data tool with 6 parameters and no annotation coverage, this leaves significant behavioral gaps unaddressed.

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, efficient sentence that front-loads the core purpose. It avoids redundancy and wastes no words, though it could be slightly more structured by separating scope from data types. Every part of the sentence contributes value, making it appropriately concise for the tool's complexity.

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 the tool's moderate complexity (6 parameters, financial data), lack of annotations, and no output schema, the description is minimally adequate. It covers the what (financial data retrieval) and scope (Hong Kong companies), but misses behavioral context, usage guidelines, and output details. The schema handles parameters well, but the description doesn't fill other gaps sufficiently for a higher score.

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?

The description mentions financial statement types (income, balance, cashflow) which align with the 'data_type' parameter, but adds no additional parameter semantics beyond what the schema provides. With 100% schema description coverage, the baseline is 3. The description doesn't compensate for any gaps because there are none in the schema, but it also doesn't enhance parameter understanding beyond the schema's thorough documentation.

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 clearly states the tool's purpose: '获取港股上市公司综合表现数据,包括利润表、资产负债表、现金流量表等财务报表数据' (Get comprehensive performance data for Hong Kong-listed companies, including income statements, balance sheets, cash flow statements, and other financial report data). It specifies the verb ('获取' - get), resource ('港股上市公司综合表现数据' - Hong Kong-listed company performance data), and scope (financial statements). However, it doesn't explicitly differentiate from sibling tools like 'company_performance' or 'company_performance_us', which appear to be similar tools for different markets.

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. It doesn't mention sibling tools like 'company_performance' (likely for other markets) or 'company_performance_us', nor does it specify prerequisites, exclusions, or contextual usage scenarios. The agent must infer usage from the tool name and description alone.

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

Related 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/guangxiangdebizi/FinanceMCP'

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