Patsnap Patent & Literature Search
About
Search global patents, journal literature, and professional information; read basic patent and literature information and patent lifecycle details; and standardize assignee names and confirm corporate hierarchies.
Available capabilities
9 callable tools
Input · Output
- Input
- text
Arguments
textThe user's complete natural-language patent retrieval intent. Pass it unchanged. Do not pass an already executable PatSnap field-code query.
This server connects to PatSnap's global patent and academic•paper databases, allowing the AI assistant to search patents and papers through separate tools and fetch details for known records. Search supports natural•language semantic retrieval, keyword retrieval, structured filters, pagination, and sorting. Patent search also supports PatSnap Boolean field queries and the professional `ls` (life sciences) and `material` domains. It can also convert a natural•language patent•search intent into an executable Boolean query, resolve an unverified patent•applicant name, and inspect a company's ancestors, children, descendants, or root group. Detail capabilities include patent bibliography, claims, descriptions, technical summaries, relations or media, paper bibliography and abstracts, and patent lifecycle information through a separate tool.
• When you need to search patents or papers around a technical problem, product direction, R&D topic, or explicit technical terms • When you need to filter results by applicant, inventor, author, organization, jurisdiction, IPC, date, legal status, or citation threshold • When you need life•sciences patent search involving medicines, therapeutic targets, diseases, chemical structures, or biological sequences • When you need material patent search involving substances, measured properties, measurement conditions, and patent•text context • When the user provides an executable PatSnap Boolean query, or a complex natural•language retrieval intent must be converted into a Boolean field query • When a patent•applicant name may be a short name, alias, former name, translation, spelling variant, or incomplete name and must be resolved to a standard assignee or company identity • When you need a confirmed company's ancestors, direct children, descendants, or root group together with each company's direct standard•assignee IDs • When you have a known patent ID, publication number, or internal paper ID and need one record's details or patent lifecycle information • Not suitable for aggregates, trends, distributions, Top•N statistics, or general chat, and not a substitute for final legal opinions, FTO conclusions, or expert review
• For `search_patent`, provide `search_strategy`. `semantic` requires `semantic_query`; `keyword` requires atomic `keywords`; `filter` requires at least one condition in `filters` or `domain_filters`; `boolean` must be exclusive as `search_strategy=["boolean"]` and requires `boolean_query` • For `search_literature`, use `semantic`, `keyword`, or `filter` with its corresponding parameters; paper search does not support `boolean`, `domain`, or `domain_filters` • Search requests may include `sort`, `limit`, and `offset`; professional patent search also requires the appropriate `domain` • For `describe_search_capability`, provide `domain` as `ls` or `material`; call this tool before constructing professional•domain filters • For `build_patent_boolean_query`, pass the user's complete natural•language patent•retrieval intent unchanged in `text`; do not pass an already executable field query • For `get_standard_assignee_name`, provide the unverified name in `query`; `limit` controls the maximum number of company candidates and standard•assignee candidates independently • For `get_corptree_hierarchy`, provide a confirmed `company_id` and select `direction` from `ancestors`, `children`, `descendants`, or `root_group`; optional parameters include `max_depth`, `company_filter`, `limit`, and `offset` • For `fetch_patent`, provide `patent_id`; optionally set `language` and `format`, and use `include` with `relations` or `media` only when explicitly needed • For `fetch_literature`, provide the internal paper ID as `paper_id`; optionally set `language` and `format` • For `fetch_patent_lifecycle`, provide an internal patent ID or publication number as `patent_id`; optionally set `language` and `format` • Detail tools accept `language` values `en`, `zh•CN`, `zh•TW`, or `ja`, and `format` values `json` or `markdown`
• `search_patent` returns ranked and paginated patent results with metadata and snippets • `search_literature` returns ranked and paginated paper results with metadata and snippets • `describe_search_capability` returns professional•domain filter fields, allowed operators, operand shapes, and fields that may appear in `domain_data`; it does not perform a search • `build_patent_boolean_query` returns an executable `data.boolean_query` • `get_standard_assignee_name` returns company candidates and standard•assignee candidates independently, with resolution statuses and match evidence • `get_corptree_hierarchy` returns the selected company and related company nodes, each with its own direct standard•assignee IDs • `fetch_patent` returns bibliography, claims, description, and technical summaries by default; `include` can add relations or media • `fetch_literature` returns basic bibliographic fields and an abstract for one paper • `fetch_patent_lifecycle` returns legal events, license or transfer records, and pledge or invalidity records • When a detail tool uses `format="markdown"`, the response carries only `response.markdown`
• Patents and papers must be searched separately with `search_patent` and `search_literature`; one search call cannot return both record types • Search pagination requires `limit` 1–100, `offset >= 0`, and `offset + limit <= 1000` • Strategies and parameters are strictly bound; omit a strategy's parameter when that strategy is absent. Patent `boolean` is exclusive and cannot be combined with another strategy, professional domain, or filters • Call `describe_search_capability` before using a non•`general` patent domain; `ls` entity filters accept public names, and `material` is used for material•related retrieval • Professional•domain fields, operators, and values must follow the capability description; do not invent fields, operators, or identifiers • `company_id` and standard•assignee `ans_id` are not interchangeable; discovering a parent, subsidiary, or root group does not automatically expand the patent•search scope • `fetch_patent` already includes fulltext•related sections by default; `include` accepts only `relations` and `media`, which add calls and latency. Lifecycle data requires a separate `fetch_patent_lifecycle` call • `fetch_literature` accepts an internal `paper_id`, not a URL; each detail tool fetches one record per call and does not support batch keys
Find patents from the last five years about solid-state battery electrolyte-interface stability, ordered by newest publication
Find highly cited papers since 2022 about large-language-model patent search
Describe the material-domain fields, then find material patents with tensile strength from 500 to 1500
Build and run a Boolean query for Toyota solid-state-battery patents since 2020
Resolve Huawei as a company and standard patent assignee