Skip to main content
Glama
Sign In

Euipo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Euipo Search Product Indications

euipo_search_product_indications
Read-onlyIdempotent

Search the EUIPO's harmonised Locarno product-indications classification (DSClass) used for registered Community design filings — "find accepted design indications for 'chair'". Returns matching indications with their Locarno class/subclass and concept id, plus raw. Example: euipo_search_product_indications({ term: "chair", locarno_class: 6, language: "en" })

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page index for pagination (default 0).
sizeNoMax results per page (default 20).
termNoText to search for within product-indication terms, e.g. "chair".
_apiKeyNoOptional: your own EUIPO client_id:client_secret; Pipeworx supplies one if omitted.
languageNoEU official language code for the search and results, e.g. "en". Required by the upstream API; defaults to "en".
locarno_classNoLocarno classification class number to restrict the search to, e.g. 6.
locarno_subclassNoLocarno classification subclass number (requires locarno_class).
parent_concept_idNoRestrict to children of this taxonomy concept id (for browsing the classification tree).

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",
-    "language": "en",
-    "locarno_class": 6,
-    "term": "chair"
-  }
-]New value: +[
+  {
+    "language": "en",
+    "locarno_class": 6,
+    "term": "chair"
+  }
+]
    • 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

A3.9/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 that by disclosing what is returned (matching indications with Locarno class/subclass and concept id, plus raw), which matters because there is no output 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?

The purpose is front-loaded in the first clause, followed by return shape and an example. It is reasonably tight, though the example call duplicates the schema's own examples array and could be trimmed.

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 read-only search tool with no output schema, the description covers purpose, return contents, and a worked example, leaving the fully documented pagination and filter parameters to the schema. It is complete enough for an agent to invoke correctly.

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 one of the 8 parameters is already documented in the schema. The description only echoes term, locarno_class, and language through the example call, adding no new constraints or format details beyond the schema baseline.

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 and resource: searches EUIPO's harmonised Locarno product-indications classification (DSClass). The phrase 'used for registered Community design filings' implicitly separates it from euipo_search_goods_services, which covers trademark goods/services, but no sibling is named explicitly.

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?

Provides a concrete usage context ('find accepted design indications for "chair"') and a full example invocation showing term, locarno_class, and language together. It gives no explicit exclusions or guidance on when to prefer euipo_search_goods_services instead, which keeps it below 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