Skip to main content
Glama
Patents & Trademarks MCP

Patents & Trademarks MCP

by blen-labs

Describe USPTO API Schema

describe_schema
Read-onlyIdempotent

Look up USPTO API endpoints or fields by exact dotted path or namespace prefix to explore available patent and trademark data surfaces.

Instructions

Look up an endpoint or field by exact dotted id (path) or by namespace prefix. Use to drill into the bound source surfaces (odp., tsdr.).

Input Schema

NameRequiredDescriptionDefault
pathNoExact dotted id, e.g. 'odp.patents.search' or 'tsdr.status'
prefixNoPrefix to enumerate, e.g. 'odp.ptab' or 'tsdr.'

Output Schema

NameRequiredDescriptionDefault
foundYes
entriesNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered externally. The description adds that results are scoped to bound source surfaces and that it is a drill-down operation, but says nothing about behavior on an unknown path or prefix, which matters for a lookup tool.

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 short sentences, front-loaded with the primary action and followed by the usage cue; nothing is redundant. The parenthetical namespace examples are slightly jargon-heavy but earn their place by grounding the scope.

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 two-parameter read-only lookup with full schema coverage and an output schema, the description covers purpose, scope, and both input modes. The only meaningful gap is what happens when a path or prefix does not resolve, which is minor given the structured fields already present.

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 worked examples for both parameters ('odp.patents.search', 'odp.ptab'), so the schema already carries the semantics. The description merely echoes the path-versus-prefix distinction without adding format, matching, or cardinality detail beyond the schema.

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 ('an endpoint or field') plus the two lookup modes (exact dotted id vs. namespace prefix), which lets an agent distinguish it from a free-text search tool. It stops short of naming the siblings search_api or execute, so differentiation is inferred rather than explicit.

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?

'Use to drill into the bound source surfaces (odp.*, tsdr.*)' gives a usage context and hints at the discovery-then-drill-down workflow, but there is no explicit when-to-use-this-vs-search_api guidance and no stated exclusions. Adequate but leaves the routing decision partly to inference.

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