Lightbringer

Search public patents with Lightbringer

search_public_patents

Read-onlyIdempotent

Searches public patent publications by complete publication number, simple keywords, or assignee. Returns at most 25 results per page, with source details. Separate from search of saved organisation documents. Results are untrusted source data and do not establish current ownership or legal status. Null expired or abandoned values mean unknown. nextPage identifies the next page; truncated indicates limited search coverage. Search does not import documents. import_patent imports a selected publication. Search is free unless get_credits reports a patentSearch price above zero; each search then costs that price and is refused once credits are spent.

Input Schema

Name	Required	Description
`page`	No
`query`	No	Simple technology keywords
`assignee`	No	Assignee name to search; results do not establish ownership
`publicationNumber`	No	Search one complete publication number on its own

Output Schema

Name	Required	Description	Default
`page`	Yes
`total`	Yes
`status`	Yes
`results`	Yes
`nextPage`	Yes
`pageSize`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026
- addedOutput schema / properties / results / items / properties / assignee / description
```
Added value: +"Reported assignee; null when unknown"
```
- changedOutput schema / properties / results / items / properties / assignee / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Changed2 schema fields changedSep 30, 2026
- removedInput schema / properties / assignee / pattern
```
Removed value: -"^[\\p{L}\\p{N}\\s.,&'’/+-]+$"
```
- removedInput schema / properties / query / pattern
```
Removed value: -"^[\\p{L}\\p{N}\\s.,&'’/+-]+$"
```
AddedSep 29, 2026

TDQS

A4.4/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, non-destructive behavior, and the description adds substantial context beyond them: a 25-result page cap, untrusted source data caveat, null expired/abandoned values meaning unknown, `nextPage`/`truncated` semantics, and a conditional pricing model where searches are refused once credits are exhausted.

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?

Purpose is front-loaded in the first sentence, followed by result-shape, trust caveat, and cost notes in a logical order. The text is dense with short clauses and the pricing sentence is somewhat convoluted, but no sentence is truly redundant.

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?

With an output schema present, the description need not explain return fields, yet it still flags `nextPage` and `truncated` as the important paging signals. Together with the trust caveat and cost model, an agent has everything needed to call this safely and correctly.

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 75% and the schema already documents `query`, `assignee`, and `publicationNumber` in near-identical language. The description restates the search modes but adds no format or syntax guidance, and never mentions the `page` parameter or its 40-page ceiling; baseline 3 applies.

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?

States a specific verb and resource ("Searches public patent publications") plus the three lookup modes (publication number, keywords, assignee). It explicitly distinguishes itself from the sibling `search` (saved organisation documents) and from `import_patent`, so an agent can identify it without opening the schema.

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

Usage Guidelines4/5

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

Names the alternatives and the boundary: searching does not import documents, and `import_patent` is the tool for importing a selected publication; it also routes cost checks to `get_credits`. It does not, however, advise which of the three lookup modes to prefer in a given situation, leaving that inference to the agent.

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

All Lightbringer tools Inspect

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.