Skip to main content
Glama
usensedata

usensedata-mcp-server-query-china-company

Official
by usensedata

query_company_software_copyright_info

Retrieve software copyright registration details for Chinese companies by entering their full name. Use this tool to verify copyright ownership and access official registration information.

Instructions

Query the registration information of an company's software copyrights by its 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

  • The handler function for the 'query_company_software_copyright_info' tool. It takes 'entName' (company full name), constructs a request with skip=0, calls the shared yushantwo API helper with product ID 'COM137', and returns the response as text content.
    async ({entName}) => {
      const requestData = {
        entName: entName,
        skip: "0"
      };
      const prodId = "COM137";
      const data = await yushantwo(requestData, prodId);
      return {
        content: [
          {
            type: "text",
            text: data,
          },
        ],
      };
    }
  • Input schema for the tool, defining 'entName' as a required string parameter representing the company full name.
    {
      entName: z.string().describe("company full name"),
    },
  • src/index.ts:206-228 (registration)
    Registration of the 'query_company_software_copyright_info' tool using server.tool(), including name, description, input schema, and inline handler function.
    server.tool(
      "query_company_software_copyright_info",
      "Query the registration information of an company's software copyrights by its 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,
          skip: "0"
        };
        const prodId = "COM137";
        const data = await yushantwo(requestData, prodId);
        return {
          content: [
            {
              type: "text",
              text: data,
            },
          ],
        };
      }
    );
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. It mentions the tool queries 'registration information' but doesn't disclose behavioral traits like whether it's read-only, what format the results are in, if there are rate limits, or authentication requirements. For a query tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with two sentences: the first states the purpose, and the second provides usage guidelines. Every sentence earns its place, and it's front-loaded with the core functionality.

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 (simple query with one parameter), lack of annotations, and no output schema, the description is adequate but incomplete. It covers purpose and usage well but lacks details on behavior, output format, or error handling. For a query tool with no structured output documentation, more context would be helpful.

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%, with the parameter 'entName' documented as 'company full name'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as 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 the registration information of an company's software copyrights by its full name.' It specifies the verb ('query'), resource ('software copyrights'), and scope ('by its full name'). However, it doesn't explicitly differentiate from siblings like query_company_trademark_list, which queries different intellectual property types.

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 names the alternative tool (fuzzy_query_company) and specifies a prerequisite step, giving clear context for when to use this tool versus alternatives.

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