Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_trademark_class_info

Read-onlyIdempotent

Look up any of the 45 international trademark classes to see what goods or services it covers, helping you pick the right classes for a clearance search.

Instructions

Look up a Nice/international trademark class (1-45).

USE THIS TOOL WHEN: You need to know what goods (classes 1-34) or
services (classes 35-45) a trademark class covers, or pick the right
classes for a clearance search.

Args:
    class_number: International class number (e.g., "9" for computer
        software, "25" for clothing, "42" for software services)

Returns:
    Class title, type (goods/services), and description.

Input Schema

NameRequiredDescriptionDefault
class_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": "get_trademark_class_infoOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.1.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description usefully adds what the tool returns (class title, type, description), but says nothing about error behavior for out-of-range values or rate limits.

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 one-line summary followed by clearly labeled USE/RETURNS/Args sections; every sentence contributes. The Args and Returns blocks are slightly verbose for a single-parameter lookup but remain scannable.

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?

With no output schema, the description correctly compensates by naming the returned fields, and the range/goods-services framing gives the agent what it needs to call the tool. Missing only edge-case behavior (invalid class numbers) and any format details for the returned description text.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does: it defines the parameter as an international class number constrained to 1-45, and gives concrete examples ('9' for computer software, '25' for clothing, '42' for software services). It could mention the string-vs-integer expectation, but the examples imply string usage.

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 and resource ('Look up a Nice/international trademark class (1-45)') and scopes it with the goods/services split. This is clearly distinguishable from siblings like tsdr_get_trademark_status or get_cpc_info, so an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

The explicit 'USE THIS TOOL WHEN' block gives concrete triggers: needing to know what a class covers, or picking classes for a clearance search. It gives no explicit alternatives or when-not-to-use cases, but the triggers are unambiguous.

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