Skip to main content
Glama
Sign In

Patent by Ouroboros Apps

by io.github.LAHutchins91
OverviewDiscussionsAdmin

Find citing and cited patents

find_patent_citations
Read-onlyIdempotent

List documents cited by a US patent and documents that cite it, using USPTO grant references and USPTO office-action citations. The PatentsView citation graph is paused. Not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "patentNumber": "<patentNumber>"
    },
    "name": "find_patent_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionNociting: documents that cite this patent. cited_by: documents this patent cites. both is the default.
patentNumberYesPatent or publication number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/open-world, so the bar is lower, and the description adds real behavioral context: the provenance of the citation data and the significant limitation that the PatentsView citation graph is paused, implying possible gaps. It does not describe result volume or pagination, keeping it short of a 5.

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 tight sentences, front-loaded with the core action, followed by a data-availability caveat and a legal disclaimer. Every sentence carries information, though the disclaimer is the least load-bearing element.

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, fully-documented two-parameter list tool with no output schema, the description covers scope (US patents), source coverage, and the paused-graph limitation. Return-value details are not needed since the schema and annotations carry the rest.

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% and the enum already explains citing/cited_by/both, so the schema does the heavy lifting. The description restates the two directions but adds no syntax or formatting detail beyond what the schema provides; baseline 3 is appropriate.

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?

Specific verb ('List') plus resource ('documents cited by a US patent and documents that cite it') and even names the data sources (USPTO grant references, office-action citations). An agent can tell this is a citation-graph tool, distinct from get_patent and search_patents, though it never explicitly contrasts itself with search_prior_art.

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?

No when-to-use or when-not-to-use guidance relative to the siblings, and no prerequisites stated. The 'PatentsView citation graph is paused' note is a data-coverage caveat rather than routing guidance, and 'Not legal advice' is a disclaimer, not usage instruction.

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