Skip to main content
Glama
Sign In

Patent by Ouroboros Apps

by io.github.LAHutchins91
OverviewDiscussionsAdmin

Search prior art

search_prior_art
Read-onlyIdempotent

Turn an idea description into a public-patent search and return the closest records the offices actually returned, with Google Patents links. Ranking counts overlapping words. It is not a patentability opinion. 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": {
      "idea": "<idea>"
    },
    "name": "search_prior_art"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaYesWhat the invention is, in plain language.
limitNoMaximum patents to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world behavior, yet the description adds traits the annotations cannot: results are records 'the offices actually returned' (provenance), ranking 'counts overlapping words' (a rough lexical heuristic the agent must not over-trust), output includes Google Patents links, and the results are not a legal conclusion.

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?

Front-loaded with the core action and output, then ranking semantics, then caveats; every sentence carries information. The final two sentences ('It is not a patentability opinion. Not legal advice.') are near-duplicates, a minor redundancy.

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?

With no output schema, the description correctly describes what comes back: closest records the offices returned plus Google Patents links, with an explanation of the ranking basis. It stops short of describing result count, empty-result behavior, or how the maxLength-constrained idea is processed, but is otherwise sufficient.

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%, so 'idea' and 'limit' are fully documented in the schema. The description only restates that the input is an idea description and adds no format, length, or query-construction guidance, 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: it converts an idea description into a public-patent search and returns the closest matching records with Google Patents links. That is enough for an agent to distinguish it from get_patent or find_patent_citations, though it never names or contrasts the sibling search_patents, which is the closest alternative.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the input is an idea description, so the agent infers when to reach for it, and the disclaimers ('not a patentability opinion', 'not legal advice') set expectations about interpretation. There are no explicit when-to-use/when-not conditions and no named alternatives, so it clears only the minimum-viable bar.

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