Crawlora MCP

usptoppubs_detail

Read-only

Fetch a USPTO Patent Public Search document's bibliographic data, abstract, description, and claims by GUID and source database. Use usptoppubs_search to find documents.

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": {
      "guid": "<guid>",
      "source": "<source>"
    },
    "name": "usptoppubs_detail"
  }
}

Input Schema

Name	Required	Description	Default
`guid`	Yes	Document GUID, e.g. from a prior search result's guid field
`source`	Yes	Source database. Allowed values: US-PGPUB, USPAT, USOCR

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / guid / description

Added value: +"Document GUID, e.g. from a prior search result's guid field"

addedInput schema / properties / source / description

Added value: +"Source database. Allowed values: US-PGPUB, USPAT, USOCR"

First observedOct 7, 2026

TDQS

A4.3/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 safety and external-dependency context is covered. The description adds nothing about quota, document size, or availability beyond the field list. Adequate but not rich given annotations carry the profile.

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 sentences, zero filler, and the primary purpose is front-loaded before the routing hint. Every clause earns its place.

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?

Output schema exists, so the description needn't explain returns; it still enumerates the key retrieved fields. Annotations cover the safety profile and required params are documented. Nothing an agent needs to call correctly is missing.

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 coverage is 100% and each parameter is documented in the schema (GUID provenance, allowed source values). The description only repeats the parameters by name, adding no format or semantics beyond what the schema provides. 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 (Fetch) and resource (a USPTO Patent Public Search document) with the exact fields returned (bibliographic data, abstract, description, claims). The named sibling usptoppubs_search makes the search-vs-retrieve boundary explicit.

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

Usage Guidelines5/5

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

Explicitly instructs 'Use usptoppubs_search to find documents', naming the alternative and the condition (you need a GUID first). This is the exact when-to-use routing an agent needs.

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

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