GleanMark Trademark Search

Search Trademarks

search_trademarks

Read-onlyIdempotent

Searches USPTO trademarks by name (14M records) and returns the closest whole-mark matches, ranked by similarity and prefix. It is not an exhaustive contains-search: multi-word marks that only contain the queried word rank low and are often cut (a KWIK query can miss KWIK REWARDS or KWIK KOPY); search_marks_by_pattern returns complete lists. A short result does not show that a name is absent from the register or available.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return
`query`	Yes	Search query for trademark name
`nice_classes`	No	Filter by Nice Classification classes (1-45)
`status_filter`	No	Filter by trademark status	all

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`results`	Yes
`total_count`	Yes
`open_in_gleanmark`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 11, 2026

addedOutput schema / properties / results / items / properties / detail_url
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / results / items / properties / mark_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / results / items / properties / owner_detail_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed1 schema field changedMar 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "open_in_gleanmark": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "filing_date": {
+            "type": "string"
+          },
+          "mark_name": {
+            "type": "string"
+          },
+          "nice_classes": {
+            "items": {
+              "type": "integer"
+            },
+            "type": "array"
+          },
+          "owner": {
+            "type": "string"
+          },
+          "registration_number": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "serial_number": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "query",
+    "total_count",
+    "results"
+  ],
+  "type": "object"
+}

Changed7 schema fields changedMar 12, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of results to return"
```
- addedInput schema / properties / nice_classes / items / maximum
```
Added value: +45
```
- addedInput schema / properties / nice_classes / items / minimum
```
Added value: +1
```
- addedInput schema / properties / nice_classes / maxItems
```
Added value: +5
```
- addedInput schema / properties / query / maxLength
```
Added value: +200
```
- addedInput schema / properties / query / minLength
```
Added value: +1
```
- addedInput schema / properties / status_filter / description
```
Added value: +"Filter by trademark status"
```
First observedFeb 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds crucial behavioral context: the non-exhaustive nature, the potential to cut multi-word marks, and the meaning of a short result. This goes beyond the annotations and helps the agent avoid misinterpretation.

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?

The description is three sentences, each carrying weight: purpose, limitation with example and alternative, and a caution. It is front-loaded with the core purpose and does not waste words on redundancies.

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?

The output schema exists, so return values are covered. The description addresses the key behavioral nuance (non-exhaustiveness) and provides the alternative tool. With 4 parameters all documented in the schema and clear usage guidance, an agent has everything needed to call this tool correctly.

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 the schema already documents all four parameters (query, limit, nice_classes, status_filter). The description adds no extra parameter-level detail beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb ('searches'), a resource ('USPTO trademarks by name'), and the result type ('closest whole-mark matches, ranked by similarity and prefix'). It also explicitly distinguishes itself from search_marks_by_pattern, so an agent can tell them apart immediately.

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?

The description clearly states when to use this tool and when not to. It notes that it is not an exhaustive contains-search, gives a concrete example (KWIK query missing KWIK REWARDS), and names the alternative (search_marks_by_pattern) that returns complete lists. It also cautions that a short result is not proof of absence, guiding interpretation.

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

All GleanMark Trademark Search 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.

Resources

Need Help?