Skip to main content
Glama

Get a federal trademark record

get_trademark
Read-onlyIdempotent

What does this federal trademark serial number identify? Returns the mark, status, owner, dates, classes, goods and services, first use, publication, pseudo mark, register date, and the TSDR record link.

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": {
      "serial": "<serial>"
    },
    "name": "get_trademark"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesUSPTO serial number, 7 to 9 digits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered externally. The description contributes beyond that by enumerating the returned fields (mark, status, owner, dates, classes, goods and services, first use, publication, pseudo mark, register date, TSDR link), which is meaningful given there is no output schema; it stops short of describing not-found or invalid-serial behavior.

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?

Two sentences, front-loaded with the core purpose before the field list. The field enumeration is long but earns its place because there is no output schema to convey return values.

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, side-effect-free lookup with no output schema, the definition supplies the essential missing piece: what comes back. Only the failure modes (unknown serial, malformed input) are absent, which is a minor gap for this complexity.

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% and the single 'serial' parameter is fully documented with a 7-9 digit pattern. The description adds no format or validation detail beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a concrete framing ('What does this federal trademark serial number identify?') and enumerates the record contents, so an agent knows this is a serial-number lookup returning a full trademark record. It is clearly distinct from the family of availability/conflict checks by being a record-retrieval operation, though it never names check_trademark_conflicts to sharpen the contrast.

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?

Usage is implied rather than stated: the question phrasing signals 'use this when you already hold a serial number and want details.' There is no explicit when-to-use/when-not-to-use guidance and no routing to sibling tools like check_trademark_conflicts for name-based searching.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources