get_portfolio_value_distribution
Analyze patent valuation distribution by technology space to identify lucrative areas. Use keywords, IPC codes, or filters like application dates and authorities to refine results. Excludes design patents.
Instructions
Assess the lucrativeness of a technology space based on the spread of estimated patent valuation (simple families). Higher value buckets indicate more lucrative technologies. Design patents are excluded. Note: Search must contain either keywords or IPC. If both are provided, IPC is prioritized.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| apply_end_time | No | Patent application end year (yyyy format). Filters by application filing date. | |
| apply_start_time | No | Patent application start year (yyyy format). Filters by application filing date. | |
| authority | No | Patent authority code (e.g., CN, US, EP, JP). Filters by patent office. Use OR for multiple, e.g., "US OR EP". | |
| ipc | No | Patent IPC classification code. Used to specify a particular technology field. | |
| keywords | No | Keywords to search within patent title and abstract/summary. Supports AND, OR, NOT logic. Example: "mobile phone AND (screen OR battery)" | |
| public_end_time | No | Patent publication end year (yyyy format). Filters by publication date. | |
| public_start_time | No | Patent publication start year (yyyy format). Filters by publication date. |
Implementation Reference
- src/index.ts:281-285 (handler)The main handler function that executes the tool logic. It constructs search parameters from the input arguments and invokes the shared PatSnap API caller with the specific 'portfolio-value' endpoint.async function getPortfolioValueDistribution(args: BasePatentArgs): Promise<ServerResult> { const params = buildCommonSearchParams(args); // No 'lang' parameter for this endpoint return callPatsnapApi('portfolio-value', params, 'get portfolio value distribution'); }
- src/index.ts:382-386 (schema)The tool schema definition registered in the ListTools response, specifying the name, description, and input schema for validation.{ name: 'get_portfolio_value_distribution', description: 'Assess the lucrativeness of a technology space based on the spread of estimated patent valuation (simple families). Higher value buckets indicate more lucrative technologies. Design patents are excluded. Note: Search must contain either keywords or IPC. If both are provided, IPC is prioritized.', inputSchema: basePatentInputSchema // Uses base schema as 'lang' is not applicable }
- src/index.ts:403-403 (registration)The registration mapping the tool name to its handler function in the dispatch map used by the CallToolRequest handler.'get_portfolio_value_distribution': getPortfolioValueDistribution, // Add new tool here
- src/index.ts:303-316 (schema)The shared base input schema referenced by the tool schema, defining properties for patent search parameters.const basePatentInputSchema = { type: 'object' as const, // Use 'as const' for stricter type checking properties: { keywords: { type: 'string', description: 'Keywords to search within patent title and abstract/summary. Supports AND, OR, NOT logic. Example: "mobile phone AND (screen OR battery)"' }, ipc: { type: 'string', description: 'Patent IPC classification code. Used to specify a particular technology field.' }, apply_start_time: { type: 'string', description: 'Patent application start year (yyyy format). Filters by application filing date.' }, apply_end_time: { type: 'string', description: 'Patent application end year (yyyy format). Filters by application filing date.' }, public_start_time: { type: 'string', description: 'Patent publication start year (yyyy format). Filters by publication date.' }, public_end_time: { type: 'string', description: 'Patent publication end year (yyyy format). Filters by publication date.' }, authority: { type: 'string', description: 'Patent authority code (e.g., CN, US, EP, JP). Filters by patent office. Use OR for multiple, e.g., "US OR EP".' } }, // Add a note about requiring keywords or IPC for most tools description: "Requires either 'keywords' or 'ipc' to be specified for a meaningful search. If both are provided, IPC is prioritized by the API." };