Nexscope

Patent Intelligence ZY

Patent Description Translation MCP

Read translated patent descriptions. Call the Patent Description Translation API via REST or MCP with your Nexscope API key.

CostRecent 10 credits / callOnline Test

Patent Description Translation 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. Translate The Technical Description

Prompt: Translate the patent technical description into [English, Chinese or Japanese] 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: Translate the patent technical description into [English, Chinese or Japanese] for [Nexscope patent ID]. Use that exact identifier and do not substitute a different patent silently.

3. Retrieve A Bounded Patent Batch

Prompt: Translate the patent technical description into [English, Chinese or Japanese] 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: Translate the patent technical description into [English, Chinese or Japanese] 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.