Skip to main content
Glama
Patents & Trademarks MCP

Patents & Trademarks MCP

by blen-labs

Search USPTO API Documentation

search_api
Read-onlyIdempotent

Search SDK methods and response-field documentation across USPTO patent and trademark sources, returning method signatures and JavaScript examples for execution.

Instructions

BM25 search over the SDK methods and response-field dictionary for all bound sources (odp, tsdr): patent applications (file wrapper), PTAB trials/appeals/interferences, petition decisions, office actions, bulk datasets, and trademark status. Returns method signatures and JavaScript examples for use in execute. Start here.

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": {
      "query": "<query>"
    },
    "name": "search_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoMax number of results to return
queryYesFree-text query over endpoint and field documentation across all bound sources (odp.*, tsdr.*).

Output Schema

NameRequiredDescriptionDefault
hitsYes
noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real behavioral context beyond that: the ranking algorithm (BM25), the breadth of indexed material, and the fact that results are method signatures plus JS examples intended for execute. It does not discuss ranking behavior details or result truncation beyond the schema's k maximum.

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?

Front-loaded with the search mechanism and index contents, then the return shape, then the routing cue. The domain enumeration is long but each item helps an agent decide whether its topic is covered; wording is dense with no filler sentences.

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?

With an output schema present, return values need not be spelled out, yet the description still characterizes them usefully. Combined with full schema coverage and rich annotations, the only minor gap is guidance on refining queries or handling empty result sets.

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%, so both query and k are already documented in the schema, establishing the baseline of 3. The description adds scope information ('across all bound sources') but no syntax, query-language, or format guidance beyond what the schema provides.

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 mechanism and resource ('BM25 search over the SDK methods and response-field dictionary'), names the sources covered (odp, tsdr) and the document families, and explicitly positions itself as the entry point ('Start here') whose output feeds 'execute'. An agent can distinguish it from execute and describe_schema without opening any 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?

'Start here' is an explicit workflow cue, and 'Returns method signatures and JavaScript examples for use in execute' tells the agent this precedes execution. There is no explicit when-not-to-use clause or direct contrast with describe_schema, so guidance is clear but not exhaustive.

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

Deploy Server

Other Tools