Skip to main content
Glama
Sign In

Uspto Office Actions

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Office Actions

search_office_actions
Read-onlyIdempotent

Search USPTO office actions (and related prosecution-history documents, e.g. petition decisions filed in the same document stream) for one patent application. Returns action type (non-final rejection, final rejection, notice of allowance, etc.), mail date, examiner employee number, and art unit — newest first. Use get_office_action_text with the returned document_id to fetch one office action's full text. Pass application_number (preferred) or patent_number.

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 10, max 100).
_apiKeyNoUSPTO ODP API key. Get free at https://data.uspto.gov/myodp. Falls back to platform key if configured.
include_rawNoDebug escape hatch: skip normal parsing and return the bare upstream HTTP status + first 500 chars of body instead (fleet #3305 — diagnosing a request shape live, no redeploy needed).
patent_numberNoGranted US patent number, as an alternative to application_number.
application_numberNoUS patent application number, digits only or formatted, e.g. "16123456" or "16/123,456".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which cover safety), the description specifies crucial behavioral traits like the sorting order ('newest first') and details exactly what specific fields are returned. This gives the AI a complete picture of the operation's outcome.

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

Conciseness5/5

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

The description is highly efficient. It front-loads the core functionality and subsequent usage advice, with no unnecessary filler, making it easy for an agent to parse quickly.

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?

Despite being a complex search tool, the description provides enough context—including the specific list of returned attributes and the default sort order—so the agent knows exactly what kind of data it will receive without needing to inspect the full return schema.

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

Parameters3/5

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

Since schema description coverage is 100%, the baseline for this dimension is 3. The description adds minor value by stating which parameter is 'preferred' but does not need to detail the structure of the parameters themselves.

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 is highly specific, clearly stating that it searches USPTO office actions and related prosecution-history documents. It also specifies the data returned (action type, mail date, examiner number), making the function unambiguous.

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?

It provides clear instructions on input preference ('application_number preferred or patent_number'). Furthermore, it provides a workflow recommendation, directing the user to a sibling tool (`get_office_action_text`) to complete the information retrieval process.

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

All Uspto Office Actions toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources