Patent Intelligence ZY
Patent Technical Description MCP
Read a patent's full technical description by ID or publication number. Call the Patent Technical Description API via REST or MCP with your Nexscope API key.
Patent Technical Description AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Read The Technical Description
Prompt: Retrieve the patent technical description for publication [publication number]. Keep the patent identifier attached to the returned information and flag unavailable content.
2. Look Up A Known Patent ID
Prompt: Retrieve the patent technical description for [Nexscope patent ID]. Use that exact identifier and do not substitute a different patent silently.
3. Retrieve A Bounded Patent Batch
Prompt: Retrieve the patent technical description for [up to 100 publication numbers]. Keep each result associated with its input number and identify any missing records.
4. Use A Family Record When Content Is Missing
Prompt: Retrieve the patent technical description for publication [publication number]. Keep the patent identifier attached to the returned information and flag unavailable content. If the requested content is unavailable, allow a related family record as a substitute and label that substitution. Otherwise leave substitution disabled and report the missing content.
What You Need to Provide
Provide either a patent ID or a publication number. Where the contract states precedence, the patent ID takes priority if both are supplied.
Patent content and reported status are research evidence, not a legal opinion or confirmation of freedom to operate.
Use returned matches and legal-status fields as research leads. They do not establish ownership, infringement, validity or freedom to operate. Dates and jurisdiction coverage must remain explicit.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_patent_description_datahttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "patent-description-data-1",
"method": "tools/call",
"params": {
"name": "nexscope_patent_description_data",
"arguments": {
"patentNumber": "US11299876B2"
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
patentId | string | optional | Patent ID (at least one of patentId and patentNumber must be provided; if both are present, patentId takes priority). Up to 100 English comma-separated values are supported. Max length: 60000 characters. |
patentNumber | string | optional | Publication/grant number (at least one of patentId and patentNumber must be provided; if both are present, patentId takes priority). Up to 100 English comma-separated values are supported. Max length: 60000 characters. Example: US11299876B2 |
replaceByRelated | string | optional | Whether to substitute with a family patent's description when the current patent's description is unavailable: 1 Yes, 0 No. Max length: 1000 characters. |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
total | integer | optional | The number of patent records returned. |
data | array | optional | Patent list, each element contains specification data. |
columns | array | optional | Rendered column definitions. |
costToken | integer | optional | Consume token. |
type | string | optional | Rendering style. |
patentId | string | optional | Patent ID. |
pn | string | optional | Public (announcement) number. |
pnRelated | string | optional | Publication number of the superseding patent; provided only when a patent family substitution is used. |
description | array | optional | Contents section of the manual. |
Example Q&A
Based on a published documentation sample, not a live tool call.
Your Question
Show the technical description for USD1140227S.
Example Answer
The sample describes an hourglass-light design through front, rear, side, top, bottom and perspective views. Its text states that broken lines depict portions outside the claimed design.
About this sample: Excerpt of a published documentation sample, not current data or a live tool call. Full source data is preserved in the published sample; arrays and long text may be shortened here.
View the Published Sample Data (JSON)
Published REST data example. Use Parameters & Response for MCP arguments when calling this tool.
Data Example
Sample request and response
Request parameters
{
"patentNumber": "USD1140227S",
"replaceByRelated": "0"
}Response
{
"code": 0,
"msg": null,
"data": {
"total": 1,
"data": [
{
"patentId": "848712f5-b5b4-4542-863f-4dd6bb2c299b",
"description": [
{
"data_format": "original",
"text": "<b class=\"d_n\">[0001]</b>FIG. 1 is a front elevational view of an hourglass light showing my new design;\n<b class=\"d_n\">[0002]</b>FIG. 2 is a rear elevational view thereof;\n<b class=\"d_n\">[0003]</b>FIG. 3 is a left side elevational view thereof;\n<b class=\"d_n\">[0004]</b>FIG. 4 is a right side elevational view thereof;\n<b class=\"d_n\">[0005]</b>FIG. 5 is a top plan view thereof;\n<b class=\"d_n\">[0006]</b>FIG. 6 is a bottom plan view thereof;\n<b class=\"d_n\">[0007]</b>FIG. 7 is a first perspective view thereof shown; and,\n<b class=\"d_n\">[0008]</b>FIG. 8 is a second perspective view thereof shown.\n<b class=\"d_n\">[0009]</b>Broken lines seen in the drawings depict portions of the hourglass light that form no part of the claimed design.\n",
"lang": "EN"
}
],
"pn": "USD1140227S"
}
],
"columns": [
{
"filterable": true,
"cellType": "text",
"field": "pn",
"sortable": true,
"title": "公开(公告)号"
},
{
"filterable": true,
"cellType": "text",
"field": "patentId",
"sortable": true,
"title": "专利Id"
},
{
"filterable": true,
"cellType": "text",
"field": "pnRelated",
"sortable": true,
"title": "替代专利的公开号(仅当使用同族专利替代时提供)"
},
{
"filterable": true,
"cellType": "text",
"field": "description",
"sortable": true,
"title": "说明书"
}
],
"type": "tableListWorkbenches"
}
}View the MCP Request & Response Format
Examples
Based on a published documentation sample, not a live tool call.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
{
"jsonrpc": "2.0",
"id": "patent-description-data-example",
"method": "tools/call",
"params": {
"name": "nexscope_patent_description_data",
"arguments": {
"patentNumber": "USD1140227S",
"replaceByRelated": "0"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "patent-description-data-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"total\":1,\"data\":[{\"patentId\":\"848712f5-b5b4-4542-863f-4dd6bb2c299b\",\"description\":[{\"data_format\":\"original\",\"text\":\"<b class=\\\"d_n\\\">[0001]</b>FIG. 1 is a front elevational view of an hourglass light showing my new design;\\n<b class=\\\"d_n\\\">[0002]</b>FIG. 2 is a rear elevational view thereof;\\n<b class=\\\"d_n\\\">[0003]</b>FIG. 3 is a left side elevational view thereof;\\n<b class=\\\"d_n\\\">[0004]</b>FIG. 4 is a right side elevational view thereof;\\n<b class=\\\"d_n\\\">[0005]</b>FIG. 5 is a top plan view thereof;\\n<b class=\\\"d_n\\\">[0006]</b>FIG. 6 is a bottom plan view thereof;\\n<b class=\\\"d_n\\\">[0007]</b>FIG. 7 is a first perspective view thereof shown; and,\\n<b class=\\\"d_n\\\">[0008]</b>FIG. 8 is a second perspective view thereof shown.\\n<b class=\\\"d_n\\\">[0009]</b>Broken lines seen in the drawings depict portions of the hourglass light that form no part of the claimed design.\\n\",\"lang\":\"EN\"}],\"pn\":\"USD1140227S\"}],\"type\":\"tableListWorkbenches\"}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"total": 1,
"data": [
{
"patentId": "848712f5-b5b4-4542-863f-4dd6bb2c299b",
"description": [
{
"data_format": "original",
"text": "<b class=\"d_n\">[0001]</b>FIG. 1 is a front elevational view of an hourglass light showing my new design;\n<b class=\"d_n\">[0002]</b>FIG. 2 is a rear elevational view thereof;\n<b class=\"d_n\">[0003]</b>FIG. 3 is a left side elevational view thereof;\n<b class=\"d_n\">[0004]</b>FIG. 4 is a right side elevational view thereof;\n<b class=\"d_n\">[0005]</b>FIG. 5 is a top plan view thereof;\n<b class=\"d_n\">[0006]</b>FIG. 6 is a bottom plan view thereof;\n<b class=\"d_n\">[0007]</b>FIG. 7 is a first perspective view thereof shown; and,\n<b class=\"d_n\">[0008]</b>FIG. 8 is a second perspective view thereof shown.\n<b class=\"d_n\">[0009]</b>Broken lines seen in the drawings depict portions of the hourglass light that form no part of the claimed design.\n",
"lang": "EN"
}
],
"pn": "USD1140227S"
}
],
"type": "tableListWorkbenches"
}
},
"isError": false
}
}