This skill guides you on how to query patent description (specification) data from the Eureka patent data platform, helping users retrieve the full-text description content of specific patents.
Core Concepts
A patent description (also called the specification) is the detailed technical document that accompanies a patent filing. It discloses how the invention works, preferred embodiments, and other technical details required by patent law. This tool queries the Eureka platform to return description data for one or more patents identified by their internal patent ID or public publication number.
Identifier priority: When both a patent ID and a publication number are provided for the same query, the patent ID takes precedence.
Family substitution: If the description for a given patent is unavailable, the tool can optionally return the description from a related family member patent instead.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| patentId | string | Conditionally | Internal patent ID. At least one of patentId or patentNumber must be provided. Multiple values separated by commas; max 100. |
| patentNumber | string | Conditionally | Publication / announcement number. At least one of patentId or patentNumber must be provided. Multiple values separated by commas; max 100. |
| replaceByRelated | string | No | Whether to substitute a family patent's description when the target patent's description is unavailable. 1 = yes, 0 = no. |
Response Fields
| Field | Type | Description |
|---|---|---|
| total | integer | Number of patent records returned |
| data | array | List of patent description objects |
| data[].patentId | string | Patent ID |
| data[].pn | string | Publication number |
| data[].pnRelated | string | Publication number of the substitute family patent (only present when family substitution is used) |
| data[].description | array | Description / specification content sections |
| columns | array | Column definitions for rendering |
| costToken | integer | Tokens consumed by the query |
| type | string | Rendering style hint |
How to call
- API endpoint：
POST /tool-eureka/descriptionData(For complete parameters/responses/error codes, seereferences/api.md） - Python script：
python scripts/eureka_description.py '<JSON 参数>' [--inline] - Cost constraints: This tool consumes credits; by default, the same parameter combination is called only once per session, and the script has a 24h local cache. On failure/empty results, do not automatically try different keywords, paginate, or change the zip code to probe repeatedly; if you need to continue searching, first explain to the user that additional consumption will be incurred.
Output strategy (default script behavior)：
- Alwayswrite the complete response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-eureka-description-<timestamp>.json（<cwd>is the working directory when the script runs, which in Claude Code is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user's task;Writing to /tmp is prohibited, and if the current directory is not writable, report an error) - Response body ≤ 8 KB: after saving to disk, print the complete JSON to stdout
- Response body > 8 KB: after saving to disk, stdout outputs only a summary (top-level fields, common counts such as
total/costToken, the length of the largest list field + the first 3 samples) - Add
--inlineto force full printing to stdout (also saved to disk)
Data reading suggestions: First look at the summary to determine whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding putting the entire JSON into the context.
Resolve authentication and credit issues
When the following abnormal situations occur, take the following measures to handle them:
Abnormal situation
- API Key not configured: The environment variable is not configured
LINKFOX_AGENT_API_KEY, andLINKFOXAGENT_API_KEY。 - Response 401 or 402 status code
- Response indicates insufficient credits or balance: The message contains "insufficient credit balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.
Measures
- Prefer using onboarding.md within the skill to guide problem resolution.
- If the onboarding.md file cannot be found, load the /linkfox-onboarding skill and handle it according to its guidance. If it is not installed, install it first:
- Fallback measure: only when all efforts with the previous two measures fail, prompt the user to follow the https://skill.linkfox.com/linkfoxskills/guide.htm guidance to obtain an API Key, or go to https://os.linkfox.com/ to top up credits.
How to Build Queries
Querying by Publication Number
When users provide a patent publication number (e.g., CN115099012A, US20230012345A1), pass it via the patentNumber parameter:
patentNumber: "CN115099012A"
Querying by Patent ID
When users provide internal patent IDs, pass them via the patentId parameter:
patentId: "abc123def456"
Batch Queries
Both patentId and patentNumber accept comma-separated values for batch lookups (up to 100):
patentNumber: "CN115099012A,US20230012345A1,EP4123456A1"
Family Substitution
When a patent's description is not available in the database and the user still wants content, enable family substitution:
patentNumber: "CN115099012A"
replaceByRelated: "1"
Usage Examples
1. Look up a single patent description by publication number
patentNumber: "CN115099012A"
2. Look up descriptions for multiple patents at once
patentNumber: "CN115099012A,US20230012345A1"
3. Look up with family substitution enabled
patentNumber: "CN115099012A"
replaceByRelated: "1"
4. Look up by patent ID
patentId: "some-patent-id"
Display Rules
- Present data faithfully: Show the returned description content clearly without altering technical details or adding subjective interpretation.
- Structured output: When the description contains multiple sections (background, summary, detailed description, claims, etc.), present them with clear headings for readability.
- Family substitution notice: If the response includes a
pnRelatedfield, explicitly inform the user that the description was sourced from a related family patent and state the substitute publication number. - Batch results: When multiple patents are returned, clearly separate each patent's content with its publication number as a heading.
- Error handling: When a query fails or returns no data, explain the reason and suggest the user verify the patent ID or publication number.
Important Limitations
- Identifier requirement: At least one of
patentIdorpatentNumbermust be provided; the tool cannot search by keyword or applicant name. - Batch limit: A maximum of 100 patents can be queried in a single request.
- Availability: Not all patents have descriptions available in the database. Use
replaceByRelated: "1"to attempt family substitution when needed. - Priority rule: If both
patentIdandpatentNumberare supplied,patentIdtakes precedence.
User Expression & Scenario Quick Reference
Applicable -- Queries about patent description / specification content:
| User Says | Scenario |
|---|---|
| "Show me the description of patent XX" | Single patent description lookup |
| "Get the full specification for these patents" | Batch patent description retrieval |
| "I need the detailed text of CN115099012A" | Lookup by publication number |
| "Can you find a family patent's description instead" | Family substitution query |
| "What does this patent describe technically" | Description content review |
Not applicable -- Needs beyond patent description data:
- Patent search by keyword, applicant, or classification
- Patent claim analysis or claim chart generation
- Patent legal status or prosecution history
- Patent landscape or statistical analysis
- Freedom-to-operate or infringement opinions
Credit consumption rules
Billed according to dynamic rules: credits consumed = 81 × max(number of returned records, 1).
Important: The services of this skill are calculated dynamically by a multiplier and may consume a large number of credits at once. The user must be reminded, and the user decides whether to continue.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- Anything you believe could be improved
Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.
For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.