Skip to main content
Glama
Sign In
industry-chain-mcp-server

industry-chain-mcp-server

by handaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

enterprise_get_enterprise_holder_info

Retrieve controlling shareholder details for any enterprise using its name, registration number, credit code, or ID. Supports multiple identifier types for flexible lookup.

Instructions

查询企业控股股东信息。

请求参数:

  • matchKeyword: 企业名称/注册号/统一社会信用代码/企业id

  • keywordType: name、nameId、regNumber、socialCreditCode

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "matchKeyword": "<matchKeyword>"
    },
    "name": "enterprise_get_enterprise_holder_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordTypeNo
matchKeywordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authorization requirements, rate limits, or side effects. The description carries the full burden but fails to provide needed context.

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?

Extremely concise with two short paragraphs. The purpose is front-loaded, and parameter list is structured. No wasted words.

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 no output schema and no description of return values, the description is incomplete. It does not explain what data the tool returns, which is critical for an information retrieval tool.

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 0%, but the description includes parameter explanations (e.g., 'matchKeyword' accepts name/registration number/credit code, 'keywordType' lists options). This adds meaning beyond the raw schema but lacks completeness (e.g., no format or validation details).

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?

Description clearly states the action ('查询') and resource ('企业控股股东信息'), indicating it queries controlling shareholder info. It is distinguishable from sibling tools like enterprise_get_enterprise_base_info, though no explicit differentiation is provided.

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?

No guidance on when to use this tool versus alternatives. The description does not specify prerequisites, limitations, or context for use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools