Skip to main content
Glama

get_portfolio_value_distribution

Analyze patent portfolio value distribution to identify lucrative technology spaces based on estimated patent valuations, excluding design patents. Requires keywords or IPC classification for search.

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
NameRequiredDescriptionDefault
keywordsNoKeywords to search within patent title and abstract/summary. Supports AND, OR, NOT logic. Example: "mobile phone AND (screen OR battery)"
ipcNoPatent IPC classification code. Used to specify a particular technology field.
apply_start_timeNoPatent application start year (yyyy format). Filters by application filing date.
apply_end_timeNoPatent application end year (yyyy format). Filters by application filing date.
public_start_timeNoPatent publication start year (yyyy format). Filters by publication date.
public_end_timeNoPatent publication end year (yyyy format). Filters by publication date.
authorityNoPatent authority code (e.g., CN, US, EP, JP). Filters by patent office. Use OR for multiple, e.g., "US OR EP".

Implementation Reference

  • The main handler function for the 'get_portfolio_value_distribution' tool. It builds URL search parameters from the input arguments and delegates to the shared 'callPatsnapApi' helper to fetch data from PatSnap API endpoint 'portfolio-value'.
    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'); }
  • Type and JSON schema definition for the input arguments accepted by the 'get_portfolio_value_distribution' tool (shared across similar patent search tools). Defines optional properties for keywords, IPC, date ranges, and authority.
    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." };
  • src/index.ts:383-386 (registration)
    Tool registration in the ListToolsRequestHandler response. Specifies the tool name, description, and references the input schema.
    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)
    Registration of the tool name mapped to its handler function in the dispatch object used by CallToolRequestHandler.
    'get_portfolio_value_distribution': getPortfolioValueDistribution, // Add new tool here
  • TypeScript type definition for the input arguments of the handler function.
    type BasePatentArgs = { keywords?: string; ipc?: string; apply_start_time?: string; apply_end_time?: string; public_start_time?: string; public_end_time?: string; authority?: string };

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KunihiroS/patsnap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server