Skip to main content
Glama
arbajian
by arbajian

odp_search_applications

Search USPTO patent applications by inventor, assignee, application number, patent number, or filing date range using Lucene query syntax.

Instructions

Search patent applications in USPTO Open Data Portal.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
application_numberNo
patent_numberNo
inventor_nameNo
assignee_nameNo
filing_date_fromNo
filing_date_toNo
offsetNo
limitNo
fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but the description details auto-quoting, wildcards, parameter translation, and AND/OR logic. However, it lacks disclosure on rate limits or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections and front-loaded purpose, but lengthy due to comprehensive examples; could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers major usage patterns and parameter details, but lacks explicit error handling or edge case descriptions; output schema is mentioned but not detailed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description provides extensive parameter documentation including mapping, auto-quoting, wildcard usage, and advanced query syntax.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Search patent applications in USPTO Open Data Portal' and contrasts with PPUBS, distinguishing it from other retrieval tools like odp_get_application.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes a 'USE THIS TOOL WHEN' section with explicit criteria, parameter mapping, and advanced query guidance, clearly indicating when to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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/arbajian/odp-patent-mcp'

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