Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tm_get_trademark

Read-onlyIdempotent

Retrieve a trademark's search-index record by 8-digit serial number. Use after tm_search_trademarks; for live status, use tsdr_get_trademark_status.

Instructions

Get a trademark's search-index record by serial number.

USE THIS TOOL WHEN: You have a serial number from tm_search_trademarks
results and want the full indexed record. For authoritative live status,
prefer tsdr_get_trademark_status.

Args:
    serial_number: 8-digit application serial number (e.g., "78787878")

Returns:
    Normalized response with the trademark record.

Input Schema

NameRequiredDescriptionDefault
serial_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tm_get_trademarkOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds the valuable behavioral fact that this returns an index record rather than live status, implying potential staleness — a meaningful distinction. It stops short of stating refresh cadence, caching, or error behavior for unknown serial numbers.

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 purpose sentence followed by clear USE WHEN and Args sections; no wasted words. The Returns line ('Normalized response with the trademark record.') is thin filler that adds little, keeping it from a 5.

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?

For a single-parameter read tool with no output schema, the description covers purpose, routing, and the one parameter's format. The return-value description is vague, but with annotations carrying the safety profile and only one input, nothing critical to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (serial_number has no description in the schema), so the description must carry the load — and it does, specifying 8-digit application serial number with a concrete example ('78787878'). That format detail is exactly what the schema omits.

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 (get), resource (trademark search-index record), and retrieval key (serial number). It also distinguishes itself from tsdr_get_trademark_status by labeling itself the 'search-index record' and the other the authoritative live status.

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?

An explicit 'USE THIS TOOL WHEN' clause gives the trigger condition (you have a serial number from tm_search_trademarks results), and it names the alternative (tsdr_get_trademark_status) with the condition that selects it (authoritative live status). No inference required.

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