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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

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)
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: it's a read-only operation (implied by 'get'), offers token reduction benefits (80-95%), and provides targeted guidance. However, it lacks details on potential errors, rate limits, or authentication requirements, which prevents a score of 5.

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

Conciseness3/5

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

The description is front-loaded with a clear purpose and quick reference, but it includes repetitive or verbose elements, such as listing sections twice (in the quick reference and 'Available sections') and adding marketing-like benefits (e.g., 'Context Efficiency Benefits'). Some sentences could be trimmed without losing essential information.

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

Completeness5/5

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

Given the tool's low complexity (1 parameter, no annotations, but with an output schema), the description is complete enough. It explains the purpose, usage, parameters, and benefits, and since an output schema exists, it doesn't need to detail return values. The description adequately covers what users need to know to invoke the tool correctly.

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?

The input schema has 0% description coverage for its single parameter 'section', but the description compensates fully by listing all available sections (e.g., 'overview', 'workflows_pfw') with brief explanations. This adds significant meaning beyond the schema, making the parameter's purpose and options clear to users.

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

Purpose4/5

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

The description clearly states the tool's purpose: to 'Get selective USPTO FPD guidance sections for context-efficient workflows.' It specifies the verb ('get'), resource ('USPTO FPD guidance sections'), and benefit ('context-efficient workflows'). However, it doesn't explicitly distinguish this tool from its siblings (e.g., document-focused tools like FPD_get_document_content_with_mistral_ocr), which would be needed for a score of 5.

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?

The description provides explicit guidance on when to use this tool versus alternatives through the 'QUICK REFERENCE' section, which maps specific questions (e.g., 'Find petitions by company/art unit') to recommended sections (e.g., 'tools'). It also lists all available sections with brief descriptions, helping users select the appropriate one based on their workflow needs.

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

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