Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

usptoppubs_search

Read-only

Search the USPTO's full-text index and return normalized patent bibliographic records. Use usptoppubs_detail for one patent's information or googlepatents_search for a separate Google Patents search.

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": {
      "q": "<q>"
    },
    "name": "usptoppubs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query text -- accepts USPTO's full Advanced Search (BRS) query syntax: field codes, date ranges, boolean/proximity operators, wildcards
numNoResults to return, default 20, max 100
pageNoResults page, 0-indexed, default 0
databasesNoComma-separated subset of databases to search. Allowed values: US-PGPUB, USPAT, USOCR. Defaults to all three

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / databases / description
      Added value: +"Comma-separated subset of databases to search. Allowed values: US-PGPUB, USPAT, USOCR. Defaults to all three"
    • addedInput schema / properties / num / description
      Added value: +"Results to return, default 20, max 100"
    • addedInput schema / properties / page / description
      Added value: +"Results page, 0-indexed, default 0"
    • addedInput schema / properties / q / description
      Added value: +"Search query text -- accepts USPTO's full Advanced Search (BRS) query syntax: field codes, date ranges, boolean/proximity operators, wildcards"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are 'normalized patent bibliographic records,' which is useful return-character context, but says nothing about rate limits, coverage, or result freshness.

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?

Two tight sentences, zero waste. The purpose is front-loaded ahead of the sibling routing guidance.

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?

An output schema exists so return values need no elaboration, and the schema fully documents all four parameters including BRS syntax. The description covers purpose and alternatives; only minor behavioral context (coverage, limits) is absent.

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% — every parameter including the required q and its BRS syntax, num/defaults, page, and databases enum-like values is fully documented in the schema. The description adds no parameter detail, so baseline 3 is appropriate.

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 (Search) and resource (USPTO's full-text index), plus what it returns (normalized patent bibliographic records). It distinguishes itself from siblings by naming usptoppubs_detail and googlepatents_search, so an agent can route without opening other schemas.

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?

Explicitly names two alternatives: usptoppubs_detail for a single patent's information and googlepatents_search for a separate Google Patents search. The routing logic is clear, though it stops short of stating when-not to use this tool (e.g., non-patent literature).

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

All Crawlora MCP 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