Skip to main content
Glama
Sign In

Euipo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Euipo Trademark

euipo_trademark
Read-onlyIdempotent

Retrieve a single EU trademark by its application or registration number from the EUIPO — "look up EUTM 018123456". Returns the full record (mark text, status, owner/representative, Nice classes, goods & services, filing/registration/expiry dates) plus raw. Example: euipo_trademark({ number: "018123456" })

Input Schema

NameRequiredDescriptionDefault
numberYesEUTM application or registration number, e.g. "018123456".
_apiKeyNoOptional: your own EUIPO client_id:client_secret; Pipeworx supplies one if omitted.

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",
-    "number": "018123456"
-  }
-]New value: +[
+  {
+    "number": "018123456"
+  }
+]
    • 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: -[
-  "number",
-  "_apiKey"
-]New value: +[
+  "number"
+]
  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 cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new context: the exact record fields returned (mark text, status, owner/representative, Nice classes, goods & services, dates) plus a note that raw data is included. It omits failure behavior for unknown or malformed numbers, which keeps it from a 5.

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 with the core action, then the return payload, then a call example — a sensible order with little waste. The example call duplicates the schema's own example and the 'application or registration number' phrasing recurs, but the redundancy is minor.

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 no output schema, the description compensates well by enumerating the returned fields and the raw payload. What remains unaddressed is error/empty behavior for invalid or nonexistent numbers, which matters for a lookup keyed on a user-supplied identifier.

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 coverage is 100%, so both parameters (number and _apiKey) are already documented, and the description only restates that the number is an application or registration number. No added syntax, format rules, or normalization guidance beyond the schema's own example.

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 ('Retrieve a single EU trademark by its application or registration number') and pins the scope to a single record, which cleanly separates it from the sibling search tools like euipo_search_trademarks. An agent knows exactly what this returns without opening the schema.

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 word 'single' plus the 'look up EUTM 018123456' phrasing makes the intended use case (known-identifier lookup) clear against the browsing/search siblings. It does not explicitly name those alternatives or state when not to use it, so it falls short of a 5.

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