patents-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging. Set to 'true' to enable. | false |
| GCP_PROJECT_ID | Yes | Your Google Cloud project ID. | |
| GOOGLE_APPLICATION_CREDENTIALS | Yes | Path to the service account JSON key file for Google Cloud authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_patentB | Fetch full details of a patent by its publication number |
| get_patent_claimsA | Fetch the full claims text of a US patent by publication number. Claims are the legal scope of the patent. |
| search_patentsB | Search patents by keyword, inventor, or technology area using Google Patents public dataset |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: fetching full patent details, fetching claims text, and searching patents. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (get_patent, get_patent_claims, search_patents) with lowercase underscores.
Three tools is appropriate for a focused patents server; not overly sparse but could benefit from one or two more specialized tools.
Covers search, full details, and claims. Missing citation or family lookups, but core patent retrieval is well-covered.