USE THIS TOOL WHEN: You encounter errors or want to verify that the ODP
is properly configured before starting research.

Returns status including:
- Configuration status (API keys, credentials)
- Connection availability
- Rate limit information

USE THIS TOOL WHEN: You need to understand what technology area a CPC
code represents, or find related classification codes.

Args:
    cpc_code: CPC code to look up (e.g., "G06" for computing, "G06N3/08" for neural networks)

Returns:
    Classification details including section, title, and description.
    For section codes (A-H, Y), returns subsection list.

USE THIS TOOL WHEN: You encounter a status code in application data
and need to understand what examination stage it represents.

Args:
    code: Status code number (e.g., "30" for "Docketed New Case")

Returns:
    Status code description and examination stage.

USE THIS TOOL WHEN: You need prosecution/file wrapper data for an
application including status, dates, and basic metadata.

Args:
    app_num: Application number without slashes or commas (e.g., "14412875")

Returns:
    Application data including filing date, status, and basic info.

USE THIS TOOL WHEN: You need comprehensive application metadata
including examiner info, art unit, and detailed status.

Args:
    app_num: Application number without slashes (e.g., "14412875")

USE THIS TOOL WHEN: You need to understand the patent family tree -
parent applications, continuations, divisionals, and CIPs.

Args:
    app_num: Application number without slashes (e.g., "14412875")

Returns:
    Continuity data showing parent/child relationships and priority claims.

USE THIS TOOL WHEN: You need to know current and historical owners
of a patent or application.

Args:
    app_num: Application number without slashes (e.g., "14412875")

USE THIS TOOL WHEN: You need to calculate the actual expiration date
of a patent accounting for USPTO delays.

Args:
    app_num: Application number without slashes (e.g., "14412875")

Args:
    app_num: Application number without slashes (e.g., "14412875")

USE THIS TOOL WHEN: You need to find priority claims to foreign
applications that may affect the effective filing date.

Args:
    app_num: Application number without slashes (e.g., "14412875")

USE THIS TOOL WHEN: You need the complete timeline of prosecution
events including office actions, responses, and fee payments.

Args:
    app_num: Application number without slashes (e.g., "14412875")

Args:
    app_num: Application number without slashes (e.g., "14412875")

USE THIS TOOL WHEN: You need to search applications with filtering
by applicant metadata, dates, or other criteria not available in PPUBS.

PARAMETER MAPPING: Simple parameter names are automatically translated to ODP
Lucene query fields and combined with AND logic:
- inventor_name → applicationMetaData.firstInventorName
- assignee_name → applicationMetaData.firstApplicantName
- patent_number → applicationMetaData.patentNumber
- application_number → applicationNumberText
- filing_date_from/to → applicationMetaData.filingDate:[start TO end]

AUTO-QUOTING & WILDCARDS: Values are automatically quoted for exact phrase
matching. Use wildcards (*) for partial matches:
- "Smith" searches for exact phrase
- "Smit*" searches for anything starting with "Smit"
- "Micro*" matches "Microsoft", "Microsystems", etc.

ADVANCED QUERIES: Pass a Lucene-style string in `query` for OR logic or
raw field names:
- 'applicationMetaData.firstInventorName:Smith OR
  applicationMetaData.firstInventorName:Jones' for multiple inventors
- Combine with other filters: query='machine learning' AND assignee_name='IBM'
  generates: (machine learning) AND applicationMetaData.firstApplicantName:"IBM"

Args:
    query: Free-text or Lucene-style query (e.g., 'neural network',
           'applicationMetaData.firstInventorName:Smith OR Jones')
    application_number: Filter by application number (exact match)
    patent_number: Filter by patent number (exact match)
    inventor_name: Filter by inventor name (matches first inventor; auto-quoted)
    assignee_name: Filter by applicant/assignee name (matches first applicant; auto-quoted)
    filing_date_from: Filing date range start (YYYY-MM-DD)
    filing_date_to: Filing date range end (YYYY-MM-DD)
    offset: Starting position (default: 0)
    limit: Max results (default: 25)
    fields: Response projection — list of ODP field names to return (e.g.,
            ['applicationNumberText', 'applicationMetaData.patentNumber',
            'applicationMetaData.filingDate']). Reduces over-fetching of
            large nested structures. Omit to return all fields (default).

Returns:
    Normalized response with matching applications.

USE THIS TOOL WHEN: You need to find bulk download datasets
available from USPTO for large-scale analysis.

Args:
    query: Search query for dataset names/descriptions
    offset: Starting position (default: 0)
    limit: Max results (default: 25)

Args:
    product_id: Dataset product identifier