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

industry-chain-mcp-server

by handaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

patent_bigdata_patent_search

Search patents by name, number, applicant, or agent. Filter by patent type and paginate results.

Instructions

专利信息搜索。

请求参数:

  • matchKeyword: 专利名称/专利申请号/公布公告号/申请人/代理机构

  • pageSize: 分页大小，一页最多获取50条数据

  • patentType: 发明申请、实用新型、发明授权、外观设计

  • keywordType: 专利名称、申请号/公开号、申请人、代理机构

  • pageIndex: 页码，从1开始

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": "patent_bigdata_patent_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageSizeNo
pageIndexNo
patentTypeNo
keywordTypeNo
matchKeywordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided. The description does not disclose whether the tool is read-only, requires authentication, or has rate limits. It fails to mention any behavioral traits beyond the basic search function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise but not highly structured. The first line is a summary, followed by a parameter list. It is not verbose, but could benefit from clearer formatting (e.g., bullet points).

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?

The description lacks information about return format, error handling, sorting, or fields returned. With no output schema, the agent is left guessing about the tool's output, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description explains each parameter's meaning in Chinese (e.g., matchKeyword lists acceptable types). It also notes the page size limit of 50, adding value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '专利信息搜索' (patent information search) is vague and essentially restates the tool name. It does not distinguish from sibling tools like patent_bigdata_patent_stats, which also deals with patents.

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 such as patent_bigdata_patent_stats. There is no mention of prerequisites, typical use cases, or exclusions.

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