Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

45 Nice classes a trademark is filed under

ud_list_meta_trademark_classes
Read-onlyIdempotent

Lists the 45 Nice trademark classes with their titles and kinds so you can identify what a named class number covers.

Instructions

The 45 Nice classes a trademark is filed under. Use it when a trademark answer names a class number and someone needs what it covers. Takes no input.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ud_list_meta_trademark_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: class, title, kind.

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNoThe day of the answer, and the page cursor of a list.
linksNoLinks of the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

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 openWorldHint=false, so the safety profile is fully covered without prose. The description's added claim 'Takes no input' is inaccurate given the optional 'fields' property, which is the one piece of behavioral misinformation present. It does not contradict the annotations, and no output description is needed because an output schema 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?

Three short sentences, front-loaded with the identity of the resource, then the trigger, then the input note. There is no filler. The final sentence is brief but is the source of the inaccuracy, so it does not fully earn its place.

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?

This is a low-complexity static reference lookup with an output schema, so return values need not be explained and the description supplies enough to select and call it. The only completeness defect is the false 'takes no input' line, which an agent may read as evidence that projection is unsupported.

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

Parameters2/5

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

Schema coverage is 100%, so the 'fields' parameter is already fully documented in the schema (comma-separated top-level keys: class, title, kind). The description does not merely omit this — it asserts 'Takes no input', which actively misleads an agent into thinking no projection control exists. That is worse than silence for a tool with one optional 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?

The description names the resource precisely ('The 45 Nice classes a trademark is filed under'), which tells an agent this is a small static reference table of classification codes. It is distinguishable from the other ud_list_meta_* siblings, which cover datasets, enums, freshness and providers. It stops short of saying the tool returns the class number plus its coverage text, but the intent is clear.

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 sentence 'Use it when a trademark answer names a class number and someone needs what it covers' gives a concrete trigger condition, which is more than most list tools offer. No exclusions or alternative tools are mentioned, but the sibling catalog contains no overlapping class-lookup tool, so there is no real ambiguity to resolve.

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