Trademarks

Get Trademark By Serial

get_trademark_by_serial

Read-onlyIdempotent

Look up a US trademark by serial number. Returns status, owner, filing/registration dates, goods/services, and classification. Requires USPTO API key (free at account.uspto.gov).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No	USPTO API key (register free at account.uspto.gov/api-manager)
`serial_number`	Yes	USPTO serial number (e.g., "97123456")

Output Schema

TableJSON Schema

Name	Required	Description
`status`	No	Current status of the trademark
`attorney`	No	Attorney name if applicable
`mark_text`	No	Text or verbal element of the mark
`owner_name`	No	Owner/applicant name
`filing_date`	No	Application filing date
`status_date`	No	Date of the current status
`raw_available`	No	Whether raw XML data was available
`serial_number`	No	USPTO serial number
`goods_services`	No	Goods and services description
`registration_date`	No	Trademark registration date
`international_class`	No	International classification number
`registration_number`	No	Trademark registration number

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attorney": {
+      "description": "Attorney name if applicable",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "filing_date": {
+      "description": "Application filing date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "goods_services": {
+      "description": "Goods and services description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "international_class": {
+      "description": "International classification number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mark_text": {
+      "description": "Text or verbal element of the mark",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "owner_name": {
+      "description": "Owner/applicant name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "raw_available": {
+      "description": "Whether raw XML data was available",
+      "type": "boolean"
+    },
+    "registration_date": {
+      "description": "Trademark registration date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "registration_number": {
+      "description": "Trademark registration number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "serial_number": {
+      "description": "USPTO serial number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Current status of the trademark",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status_date": {
+      "description": "Date of the current status",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "api_key": "your-trademarks-api-key",
+    "serial_number": "97123456"
+  },
+  {
+    "serial_number": "90876543"
+  }
+]

First observedApr 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint. Description adds useful behavioral context: requires authentication (USPTO API key) and lists return data fields. No contradictions.

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, well-structured, front-loaded with purpose. Every sentence adds value with no redundancy.

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?

Given tool simplicity (2 required params, no enums, output schema present), description adequately covers purpose, return data, auth requirement. Complete for context.

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% with both parameters described. Description does not add significant meaning beyond schema; it reiterates API key requirement which is already in schema. Baseline 3 appropriate.

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?

Description explicitly states 'Look up a US trademark by serial number' with specific verb and resource. It distinguishes from sibling tools like get_trademark_by_registration and search_trademarks by focusing on serial number lookup.

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

Usage Guidelines3/5

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

Description mentions required API key but does not explain when to use this tool versus alternatives like get_trademark_by_registration or search_trademarks. No explicit when-not or exclusion criteria provided.

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

All Trademarks 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.