Skip to main content
Glama
Sign In

Patent by Ouroboros Apps

by io.github.LAHutchins91
OverviewDiscussionsAdmin

Search patents

search_patents
Read-onlyIdempotent

Search public US patent records by keywords, claim language, CPC class, assignee, inventor, or grant date. Every number in the result was returned by USPTO. Not legal advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_patents"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpcNoCPC symbol, such as H04L or C07H19/207.
limitNoMaximum hits, 1 to 25.
claimsNoClaim language. USPTO matches these words across the file wrapper.
dateToNoGrant or publication date to, YYYY-MM-DD.
assigneeNoApplicant or assignee name.
dateFromNoGrant or publication date from, YYYY-MM-DD.
inventorNoInventor name.
keywordsNoWords to find in the application or title and abstract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / claims / description
      Previous value: -"Claim language. EPO searches claim text. USPTO matches these words across the file wrapper."New value: +"Claim language. USPTO matches these words across the file wrapper."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false-equivalent safety profile, so the bar is lower. The description adds data-provenance context ('Every number in the result was returned by USPTO') and a liability disclaimer, but says nothing about result ordering, whether more hits exist beyond the limit, or truncation behavior.

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?

Three short sentences, with the capability statement front-loaded and no wasted clauses. The provenance and disclaimer sentences are brief, though the disclaimer is boilerplate that occupies limited space for little selection value.

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?

For a read-only search tool whose annotations cover the safety profile, the description is nearly complete. However, with no output schema, it leaves unaddressed how results are shaped or whether the response indicates additional matches beyond 'limit', which an agent would want before setting a limit.

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?

Schema description coverage is 100% across all 8 parameters, so the schema already documents formats like YYYY-MM-DD and the 1-25 limit range. The description's facet list roughly mirrors the schema names and adds no syntax or matching-behavior detail beyond it, so baseline 3 applies.

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?

States a specific verb and resource (search public US patent records) and enumerates the searchable facets — keywords, claim language, CPC class, assignee, inventor, grant date. An agent can tell it apart from get_patent or find_patent_citations by the fact that it is a facet-based query rather than a lookup, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus search_prior_art, find_patent_citations, or get_patent, and no exclusions or prerequisites. 'Not legal advice' is a liability disclaimer, not usage guidance, so the agent gets no routing help.

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

All Patent by Ouroboros Apps 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