Skip to main content
Glama
Sign In

Euipo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Euipo Search Trademarks

euipo_search_trademarks
Read-onlyIdempotent

Search EU trademarks (EUTM) at the EUIPO — "find EU trademarks containing NIKE in Nice classes 9 and 25". Use for EU brand clearance and competitor trademark portfolios. Returns matching marks (application number, mark text, status, owner, Nice classes, filing date) plus raw. Example: euipo_search_trademarks({ verbal_element: "nike", nice_classes: [9, 25], status: "REGISTERED" })

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page index for pagination (default 0).
sizeNoMax results per page (default 20, max 100).
queryNoAdvanced: raw RSQL filter passed through verbatim (e.g. verbalElement=="*nike*";niceClasses=in=(9,25)). Overrides the friendly params above.
statusNoTrademark status filter, e.g. "REGISTERED", "APPLICATION_FILED", "EXPIRED". Comma-separate for multiple.
_apiKeyNoOptional: your own EUIPO client_id:client_secret; Pipeworx supplies one if omitted.
applicantNoApplicant / owner name to match, e.g. "Nike Innovate".
nice_classesNoNice classification classes to filter by, e.g. [9, 25].
verbal_elementNoText/word element of the mark to match (wildcards added automatically), e.g. "nike". Multi-word values are quoted safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-euipo-client-id:your-euipo-client-secret",
-    "nice_classes": [
-      9,
-      25
-    ],
-    "status": "REGISTERED",
-    "verbal_element": "nike"
-  },
-  {
-    "_apiKey": "your-euipo-client-id:your-euipo-client-secret",
-    "applicant": "Apple Inc.",
-    "nice_classes": [
-      42
-    ]
-  }
-]New value: +[
+  {
+    "nice_classes": [
+      9,
+      25
+    ],
+    "status": "REGISTERED",
+    "verbal_element": "nike"
+  },
+  {
+    "applicant": "Apple Inc.",
+    "nice_classes": [
+      42
+    ]
+  }
+]
    • changedInput schema / properties / _apiKey / description
      Previous value: -"EUIPO OAuth credentials as \"client_id:client_secret\" from dev.euipo.europa.eu."New value: +"Optional: your own EUIPO client_id:client_secret; Pipeworx supplies one if omitted."
    • changedInput schema / required
      Previous value: -[
-  "_apiKey"
-]New value: +[]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond them by enumerating the returned fields (application number, mark text, status, owner, Nice classes, filing date) and showing a concrete invocation, though it says nothing about result caps, pagination, or the API-key behavior handled in the schema.

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 sentences, front-loaded with purpose, then usage, then return shape and an example — no filler. The example overlaps somewhat with the schema's own 'examples' block, which is the only wasted motion.

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 8 optional parameters and no output schema, the description does the right work by listing the return fields and giving a combined-parameter example. Missing only secondary details (pagination defaults, multi-status comma syntax) that the schema already covers, so nothing critical is absent.

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%, so every parameter including the advanced 'query' RSQL override and pagination is already documented in structured data. The description's example does demonstrate how verbal_element, nice_classes and status compose in practice, which is a modest semantic addition, but the baseline of 3 is appropriate when the schema carries the parameter burden.

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 ('Search EU trademarks (EUTM) at the EUIPO') with the exact scope of the search — verbal element plus Nice classes. It is immediately distinguishable from siblings like euipo_search_designs or euipo_trademark, which cover different record types or lookups.

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?

Explicitly names the use cases: 'EU brand clearance and competitor trademark portfolios.' That gives clear when-to-use context, but it never states when NOT to use it or points to a sibling (e.g., euipo_trademark for a single known mark), so routing is good but not complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Euipo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources