Skip to main content
Glama
john-walkoe

USPTO Final Petition Decisions MCP Server

by john-walkoe

FPD_get_guidance

Retrieve targeted USPTO Final Petition Decisions guidance sections to reduce context usage and optimize patent analysis workflows.

Instructions

Get selective USPTO FPD guidance sections for context-efficient workflows.

🎯 QUICK REFERENCE - What section for your question?

πŸ” "Find petitions by company/art unit" β†’ tools 🚩 "Identify petition red flags" β†’ red_flags πŸ“„ "Download petition documents" β†’ documents 🀝 "Correlate petitions with prosecution" β†’ workflows_pfw βš–οΈ "Analyze petition + PTAB patterns" β†’ workflows_ptab πŸ“Š "Citation quality + petition correlation" β†’ workflows_citations 🏒 "Complete portfolio due diligence" β†’ workflows_complete πŸ“š "Research CFR rules with Assistant" β†’ workflows_assistant 🎯 "Ultra-minimal PFW + FPD workflows" β†’ ultra_context πŸ’° "Reduce extraction costs" β†’ cost

Available sections:

  • overview: Available sections and MCP overview (default)

  • workflows_pfw: FPD + PFW integration workflows

  • workflows_ptab: FPD + PTAB integration workflows

  • workflows_citations: FPD + Citations integration workflows

  • workflows_complete: Four-MCP complete lifecycle analysis

  • workflows_assistant: Pinecone Assistant + FPD research workflows

  • tools: Tool catalog, progressive disclosure, parameters

  • red_flags: Petition red flag indicators and CFR rules

  • documents: Document extraction, downloads, proxy configuration

  • ultra_context: PFW fields parameter + ultra-minimal workflows

  • cost: Cost optimization for document extraction

Context Efficiency Benefits:

  • 80-95% token reduction (2-8KB per section vs 62KB total)

  • Targeted guidance for specific workflows

  • Same comprehensive content organized for efficiency

  • Consistent pattern with PFW MCP

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNooverview

Implementation Reference

  • The primary handler function for the 'FPD_get_guidance' tool. It takes a 'section' parameter and delegates to get_guidance_section from tool_reflections.py to return the appropriate guidance markdown.
    @mcp.tool(name="FPD_get_guidance")
    async def fpd_get_guidance(section: str = "overview") -> str:
        """Get selective USPTO FPD guidance sections for context-efficient workflows.
    
    🎯 QUICK REFERENCE - What section for your question?
    
    πŸ” "Find petitions by company/art unit" β†’ tools
    🚩 "Identify petition red flags" β†’ red_flags
    πŸ“„ "Download petition documents" β†’ documents
    🀝 "Correlate petitions with prosecution" β†’ workflows_pfw
    βš–οΈ "Analyze petition + PTAB patterns" β†’ workflows_ptab
    πŸ“Š "Citation quality + petition correlation" β†’ workflows_citations
    🏒 "Complete portfolio due diligence" β†’ workflows_complete
    πŸ“š "Research CFR rules with Assistant" β†’ workflows_assistant
    🎯 "Ultra-minimal PFW + FPD workflows" β†’ ultra_context
    πŸ’° "Reduce extraction costs" β†’ cost
    
    Available sections:
    - overview: Available sections and MCP overview (default)
    - workflows_pfw: FPD + PFW integration workflows
    - workflows_ptab: FPD + PTAB integration workflows
    - workflows_citations: FPD + Citations integration workflows
    - workflows_complete: Four-MCP complete lifecycle analysis
    - workflows_assistant: Pinecone Assistant + FPD research workflows
    - tools: Tool catalog, progressive disclosure, parameters
    - red_flags: Petition red flag indicators and CFR rules
    - documents: Document extraction, downloads, proxy configuration
    - ultra_context: PFW fields parameter + ultra-minimal workflows
    - cost: Cost optimization for document extraction
    
    Context Efficiency Benefits:
    - 80-95% token reduction (2-8KB per section vs 62KB total)
    - Targeted guidance for specific workflows
    - Same comprehensive content organized for efficiency
    - Consistent pattern with PFW MCP"""
        try:
            return get_guidance_section(section)
        except Exception as e:
            logger.error(f"Unexpected error in get guidance: {str(e)}")
            return f"Error: Internal error - {str(e)}"
  • Core helper function that implements the logic for the FPD_get_guidance tool by selecting and returning the appropriate guidance section based on the input parameter.
    def get_guidance_section(section: str = "overview") -> str:
        """
        Get selective USPTO FPD guidance sections for context-efficient workflows.
    
        Args:
            section: Section name (default: "overview")
    
        Returns:
            Markdown-formatted string for requested section
        """
        sections = {
            "overview": _get_overview_section(),
            "workflows_pfw": _get_workflows_pfw_section(),
            "workflows_ptab": _get_workflows_ptab_section(),
            "workflows_citations": _get_workflows_citations_section(),
            "workflows_complete": _get_workflows_complete_section(),
            "workflows_assistant": _get_workflows_assistant_section(),
            "tools": _get_tools_section(),
            "red_flags": _get_red_flags_section(),
            "documents": _get_documents_section(),
            "ultra_context": _get_ultra_context_section(),
            "cost": _get_cost_section()
        }
    
        if section not in sections:
            return f"Error: Section '{section}' not found. Available sections: {', '.join(sections.keys())}"
    
        return sections[section]
  • The @mcp.tool decorator registers the fpd_get_guidance function with the name 'FPD_get_guidance' in the FastMCP server.
    @mcp.tool(name="FPD_get_guidance")
  • The function signature defines the input schema: optional 'section' string parameter (default 'overview') and str return type. FastMCP uses this for tool schema generation.
    async def fpd_get_guidance(section: str = "overview") -> str:
  • Self-description of the tool within the guidance content generated by the tool itself.
    - **FPD_get_guidance**: Context-efficient sectioned guidance (this tool)

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/john-walkoe/uspto_fpd_mcp'

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