Skip to main content
Glama
usensedata

usensedata-mcp-server-query-china-company

Official
by usensedata

query_company_overseas_investments

Query overseas investment details for Chinese companies, including investment amounts, shareholding ratios, and shareholder types, using the company's full name.

Instructions

Query external investment information, such as the amount, shareholding ratio, shareholder type, etc., by the company's full name. Please use the fuzzy query tool to obtain the company full name before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entNameYescompany full name

Implementation Reference

  • Handler function that takes the company full name, calls the yushantwo helper with prodId 'COM045' to query overseas investments, and returns the result as text content.
    async ({entName}) => {
      const requestData = {
        entName: entName
      };
      const prodId = "COM045";
      const data = await yushantwo(requestData, prodId);
      return {
        content: [
          {
            type: "text",
            text: data,
          },
        ],
      };
    }
  • Zod input schema requiring 'entName' as a string (company full name).
    {
      entName: z.string().describe("company full name"),
    },
  • src/index.ts:160-181 (registration)
    Registration of the tool using server.tool, including name, description, input schema, and inline handler.
    server.tool(
      "query_company_overseas_investments",
      "Query external investment information, such as the amount, shareholding ratio, shareholder type, etc., by the company's full name. Please use the fuzzy query tool to obtain the company full name before calling this tool.",
      {
        entName: z.string().describe("company full name"),
      },
      async ({entName}) => {
        const requestData = {
          entName: entName
        };
        const prodId = "COM045";
        const data = await yushantwo(requestData, prodId);
        return {
          content: [
            {
              type: "text",
              text: data,
            },
          ],
        };
      }
    );
  • Core helper function that encrypts the request to the Yushan API, sends it via POST, decrypts the response, and returns the data. Used by multiple tools including this one.
    async function yushantwo(requestData: RequestData, prodId: string): Promise<string> {
      const url = "***";
      const reqTime = Date.now();
      const requestSN = Array.from({ length: 32 }, () => "ABCDEFGHJKMNPQRSTWXYZabcdefhijkmnprstwxyz2345678"[Math.floor(Math.random() * 58)]).join("");
    
      const requestBody = JSON.stringify({
        prod_id: prodId,
        req_data: requestData,
        req_time: reqTime,
        request_sn: requestSN,
      });
      
      // 加密请求数据
      const encryptedRequest = encrypt(requestBody, apiKey);
    
      const headers = {
        AES_KEY: apiKey,
        ACCT_ID: apiUserId,
        ENCODE: "AES256",
      };
    
      try {
        const response = await fetch(url, {
          method: "POST",
          headers: headers,
          body: encryptedRequest,
        });
    
        const responseText = await response.text();
        
        // 解密返回数据
        const decryptedString = decrypt(responseText, apiKey);
        return decryptedString;
      } catch (e) {
        console.error("Error:", e);
        return "error";
      }
    }
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. While it mentions that the tool queries investment information, it lacks details about behavioral traits such as whether this is a read-only operation, potential rate limits, authentication requirements, error handling, or what the return format looks like. For a query tool with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 and well-structured, consisting of two sentences that efficiently convey the tool's purpose and usage guidelines. Every sentence earns its place: the first explains what the tool does, and the second provides critical prerequisite information. There is no wasted verbiage or redundancy.

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 complexity (a single-parameter query with no output schema and no annotations), the description is partially complete. It adequately covers the purpose and usage guidelines but lacks details on behavioral transparency (e.g., read/write nature, response format) and parameter semantics beyond what the schema provides. For a query tool, this leaves the agent with insufficient context about what to expect from the tool's operation.

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 schema description coverage is 100%, with the single parameter 'entName' fully documented as 'company full name'. The description adds minimal value beyond this, only reiterating that the tool operates 'by the company's full name' and suggesting the fuzzy query tool to obtain it. No additional semantic context (e.g., format requirements, examples, or constraints) is provided, so the baseline score of 3 is appropriate given the schema does the heavy lifting.

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: 'Query external investment information, such as the amount, shareholding ratio, shareholder type, etc., by the company's full name.' This specifies the verb ('query'), resource ('external investment information'), and scope ('by the company's full name'), making it easy to understand what the tool does. However, it doesn't explicitly distinguish this tool from its siblings beyond mentioning the fuzzy query tool as a prerequisite.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'Please use the fuzzy query tool to obtain the company full name before calling this tool.' This clearly states a prerequisite and references an alternative tool (fuzzy_query_company) for obtaining the required parameter. It effectively tells the agent when to use this tool (after obtaining the exact company name) and what to use instead for the preliminary step.

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/usensedata/usensedata-mcp-server-query-china-company'

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