Skip to main content
Glama
hsiangjenli

GPSS Patent Search MCP

by hsiangjenli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
USER_CODEYesYour API code for GPSS Patent Search

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
tool_search_patents_tools_search_patents_postB

MCP Tool endpoint for patent search.

This tool searches the GPSS (Global Patent Search System) for patents matching your keywords. Authentication is handled automatically via the USER_CODE environment variable.

Simply provide your search keywords and optional filters. The tool will:

  1. Automatically read USER_CODE from the environment

  2. Send the request to GPSS API

  3. Return parsed results with patent numbers, titles, abstracts, and inventor info

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "success": true,
  "data": "unknown_type",
  "request_params": "unknown_type"
}

  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}
tool_get_databases_tools_get_available_databases_postC

MCP Tool endpoint for getting available databases.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • databases: Mapping of region -> database code -> description. Each database entry is a human-friendly description derived from the PatDB enum.

    • Example:

{
  "success": true,
  "databases": {
    "key": "value"
  }
}
tool_get_examples_tools_get_search_examples_postC

MCP Tool endpoint for getting search examples.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "success": true,
  "examples": {
    "key": "value"
  }
}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

The three tools serve clearly distinct purposes: searching patents, listing available databases, and retrieving search examples. There is no meaningful overlap in intent, so an agent can select the correct tool without confusion.

Naming Consistency3/5

All three names follow the same (verbatim auto-generated) pattern of 'tool_x_tools_x_post', so the convention is technically consistent. However, the redundant, verbose, and double-encoded structure is awkward and hard to read, making names less predictable than a clean verb_noun scheme.

Tool Count4/5

Three tools—one core search plus two metadata helpers—is slightly thin but well-scoped for a focused patent search server. Nothing extraneous is present.

Completeness3/5

The core search, database listing, and example retrieval are covered, but there is no tool to fetch full details for a specific patent number and no apparent support for citation, family, or document retrieval. These are notable gaps for a patent-search domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources