Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_trademark_status_code

Read-onlyIdempotent

Interpret a numeric USPTO trademark status code to reveal its meaning and prosecution stage, such as 700 for Registered or 686 for Published for opposition.

Instructions

Look up a USPTO trademark status code meaning.

USE THIS TOOL WHEN: Trademark data contains a numeric status code you
need to interpret (e.g., "700" = Registered, "686" = Published for
opposition).

Args:
    code: Trademark status code (e.g., "700")

Returns:
    Status code description and prosecution stage.

Input Schema

NameRequiredDescriptionDefault
codeYes

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds useful behavioral context by stating what is returned ('Status code description and prosecution stage'), which the annotations do not provide.

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?

Purpose is front-loaded, followed by a clear usage trigger and Args/Returns blocks. Efficient and scannable; the Args section lightly restates the schema but the structure is sound.

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, read-only, single-parameter lookup with no output schema, the description covers what the tool does, when to reach for it, and what it returns. Nothing essential an agent needs to invoke it correctly is missing.

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 schema's bare 'Code' string gives little, but the description compensates by naming the parameter as a 'Trademark status code' and supplying concrete value examples with meanings. This adds real semantic value beyond the schema for the single required parameter.

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?

States a specific verb (look up) and resource (USPTO trademark status code meaning), with the domain qualifier 'USPTO trademark' disambiguating it from the generic sibling get_status_code. However, it does not explicitly contrast itself with that sibling or with tsdr_get_trademark_status.

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 'USE THIS TOOL WHEN' line gives a concrete triggering condition ('Trademark data contains a numeric status code you need to interpret') and reinforces it with real examples (700=Registered, 686=Published for opposition). No when-not or explicit alternative routing is offered, so it stops short of 5.

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