Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tsdr_get_trademark_image

Read-onlyIdempotent

Fetch the base64-encoded drawing of a trademark's design or stylized word mark using its serial number.

Instructions

Get the mark image (drawing) for a trademark as base64.

USE THIS TOOL WHEN: You need the visual representation of a design mark
or stylized word mark.

Args:
    serial_number: 8-digit application serial number (e.g., "78787878")

Returns:
    Dictionary with base64-encoded image data.

Input Schema

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds the genuinely useful behavioral fact that the payload is a base64-encoded image rather than a URL or rendered file, which an agent must know to handle the result; it says nothing about rate limits or what happens when no image exists.

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 purpose sentence followed by clearly labelled USE THIS TOOL WHEN / Args / Returns sections, with no filler. The only minor redundancy is restating 'base64' in the Returns line already implied by the opening sentence.

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?

There is no output schema, so the description correctly steps in to describe the return shape (dictionary with base64 image data). Combined with the single required parameter being fully specified, an agent has what it needs; only edge cases (missing image, non-image marks) are unaddressed.

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 coverage is 0% and the schema only says 'Serial Number' as an unannotated string, so the description carries the burden. It supplies the required format and an example ('8-digit application serial number, e.g., "78787878"'), which is exactly the missing guidance, though it does not say what happens with a malformed number.

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 ('Get the mark image (drawing) for a trademark as base64') and sharpens it with the qualifier 'design mark or stylized word mark'. This clearly separates it from the text-oriented siblings like tsdr_get_trademark_status or tsdr_list_trademark_documents without needing to name them.

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' block gives an explicit positive trigger (need the visual representation of a design/stylized mark). It does not name a contrasting alternative (e.g., tm_get_trademark for textual mark data) or state when the tool is unnecessary, so it stops just short of full routing guidance.

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