Skip to main content
Glama
Xxx00xxX33

FinanceMCP

by Xxx00xxX33

company_performance_us

Retrieve comprehensive U.S. company performance data including income statements, balance sheets, cash flow statements, and financial indicators for analysis.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ts_codeYes美股代码,如'NVDA'表示英伟达,'AAPL'表示苹果,'TSLA'表示特斯拉
data_typeYes数据类型:income(利润表)、balance(资产负债表)、cashflow(现金流量表)、indicator(财务指标)
start_dateYes起始日期,格式为YYYYMMDD,如'20230101'
end_dateYes结束日期,格式为YYYYMMDD,如'20231231'
periodNo特定报告期,格式为YYYYMMDD,如'20231231'表示2023年年报。指定此参数时将忽略start_date和end_date

Implementation Reference

  • Core handler function that processes input parameters, selects the appropriate Tushare API endpoint based on data_type (income, balance, cashflow, indicator), fetches financial data, applies specific formatters, and returns formatted markdown content or error response.
    async run(args: { 
      ts_code: string; 
      data_type: string; 
      start_date: string;
      end_date: string;
      period?: 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 = 'us_income';
            formatFunction = formatUsIncomeData;
            break;
          case 'balance':
            apiInterface = 'us_balancesheet';
            formatFunction = formatUsBalanceData;
            break;
          case 'cashflow':
            apiInterface = 'us_cashflow';
            formatFunction = formatUsCashflowData;
            break;
          case 'indicator':
            apiInterface = 'us_fina_indicator';
            formatFunction = formatUsIndicatorData;
            break;
          default:
            throw new Error(`不支持的数据类型: ${args.data_type}`);
        }
    
        const result = await fetchUsFinancialData(
          apiInterface,
          args.ts_code,
          args.period,
          args.start_date,
          args.end_date,
          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 defining parameters for the tool: ts_code (US stock code), data_type (enum: income/balance/cashflow/indicator), start_date, end_date, optional period.
    parameters: {
      type: "object",
      properties: {
        ts_code: {
          type: "string",
          description: "美股代码,如'NVDA'表示英伟达,'AAPL'表示苹果,'TSLA'表示特斯拉"
        },
        data_type: {
          type: "string",
          description: "数据类型:income(利润表)、balance(资产负债表)、cashflow(现金流量表)、indicator(财务指标)",
          enum: ["income", "balance", "cashflow", "indicator"]
        },
        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"
        }
      },
      required: ["ts_code", "data_type", "start_date", "end_date"]
    },
  • src/index.ts:379-386 (registration)
    Tool registration in MCP stdio server: switch case in CallToolRequestSchema handler that extracts arguments and invokes companyPerformance_us.run().
    case "company_performance_us": {
      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;
      return normalizeResult(await companyPerformance_us.run({ ts_code, data_type, start_date, end_date, period }));
    }
  • Tool registration in HTTP server: switch case in tools/call handler that extracts arguments and invokes companyPerformance_us.run().
    case 'company_performance_us':
      return await companyPerformance_us.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,
      });
  • Helper function to fetch US financial data from Tushare API: constructs POST request, handles response, parses fields/items into object array.
    async function fetchUsFinancialData(
      apiInterface: string,
      ts_code: string,
      period?: string,
      start_date?: string,
      end_date?: 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;
      }
    
      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?

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions what data is returned, it doesn't describe important behavioral aspects: whether this is a read-only operation, potential rate limits, authentication requirements, data freshness, error conditions, or response format. For a financial data tool with 5 parameters, this is a significant gap in transparency.

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 Chinese sentence that states the core purpose and lists the four data types. There's no wasted verbiage or redundant information. However, it could be slightly more structured by separating the purpose from the data type enumeration for better readability.

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

Completeness2/5

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

Given the complexity (financial data tool with 5 parameters, no annotations, no output schema), the description is incomplete. It doesn't address key contextual elements: what the output looks like, data format, pagination if any, error handling, or performance characteristics. For a tool that returns potentially complex financial data, users need more context about what to expect from the response.

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 description coverage is 100%, so the schema already fully documents all 5 parameters. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain parameter interactions, default behaviors, or provide examples of valid combinations. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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 US-listed companies) and specifies the data types included (income statement, balance sheet, cash flow statement, financial indicators). It distinguishes from sibling tools like 'company_performance' and 'company_performance_hk' by specifying US stocks. However, it doesn't explicitly mention the verb 'retrieve' or 'fetch' - it uses '获取' which is equivalent.

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 when to choose this over 'company_performance' (likely for non-US stocks) or 'company_performance_hk' (Hong Kong stocks), nor does it provide any context about prerequisites, limitations, or typical use cases. The user 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

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/Xxx00xxX33/FinanceMCP'

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