GleanMark Trademark Search

Search Marks by Owner

search_by_owner

Read-onlyIdempotent

Search for trademark owners by name. Use this to resolve or list candidate owners, not for owner counts, rankings, prosecution snapshots, or recent activity checks. Returns matching companies/individuals with their trademark portfolio statistics (total marks, live/dead counts, registered/pending).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of owners to return
`owner_name`	Yes	Owner name to search for (company or individual)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`owners`	Yes
`open_in_gleanmark`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 11, 2026
- addedOutput schema / properties / owners / items / properties / detail_url
```
Added value: +{
+  "type": "string"
+}
```

Changed4 schema fields changedMar 17, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of owners to return"

addedInput schema / properties / owner_name / maxLength
```
Added value: +200
```
addedInput schema / properties / owner_name / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "open_in_gleanmark": {
+      "type": "string"
+    },
+    "owners": {
+      "items": {
+        "properties": {
+          "canonical_name": {
+            "type": "string"
+          },
+          "dead_marks": {
+            "type": "integer"
+          },
+          "live_marks": {
+            "type": "integer"
+          },
+          "normalized_name": {
+            "type": "string"
+          },
+          "pending_marks": {
+            "type": "integer"
+          },
+          "registered_marks": {
+            "type": "integer"
+          },
+          "similarity_score": {
+            "type": "number"
+          },
+          "total_marks": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "owners"
+  ],
+  "type": "object"
+}

First observedFeb 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context about the return content: 'portfolio statistics (total marks, live/dead counts, registered/pending)' – information not present in the annotations. It does not disclose potential quirks like pagination, but given the low complexity and annotation coverage, this is adequate.

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 two sentences with no fluff. The core purpose is front-loaded ('Search for trademark owners by name'), followed by immediate exclusions and a summary of return data. Every word adds value, making it an exemplar of conciseness.

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 simple search tool with two parameters, the description covers its purpose, usage scope, and return content. Since an output schema is present, the description need not detail return formats. It could optionally mention ordering or fuzzy matching, but nothing essential is missing for correct invocation.

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%, with both parameters (owner_name and limit) documented. The description does not add significant semantics beyond what the schema provides; it merely restates that it searches by name. With complete schema documentation, a baseline score of 3 is appropriate, and the description doesn't need to compensate.

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 clearly states the tool's function: 'Search for trademark owners by name.' It explicitly specifies the scope ('resolve or list candidate owners') and distinguishes it from other operations ('not for owner counts, rankings, prosecution snapshots, or recent activity checks'), which sets it apart from siblings like get_top_filers and count_filings_by_period.

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 provides explicit guidance on when to use the tool and when not to: 'Use this to resolve or list candidate owners, not for owner counts, rankings, prosecution snapshots, or recent activity checks.' This directly routes the agent to appropriate alternatives for other purposes, fulfilling the usage guidelines dimension completely.

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?