Skip to main content
Glama
Sign In

Euipo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Euipo Search Persons

euipo_search_persons
Read-onlyIdempotent

Search applicants or representatives on record with the EUIPO for trademark/design procedures — "find the EUIPO representative record for a named law firm". Each row carries its role (e.g. APPLICANT_BUSINESS, APPLICANT_INDIVIDUAL, REPRESENTATIVE_EUIPO_PROFESSIONAL) and its source. Privacy: street/city/postal-code address details are withheld for individual persons — only country-level location is kept; business/association entities keep their registered address. Example: euipo_search_persons({ name: "adidas", role: "applicant", country: "DE" })

Input Schema

NameRequiredDescriptionDefault
cityNoCity to filter by, e.g. "Alicante". Only meaningful for business/association entities (withheld for individuals in the response).
nameNoName to search for, e.g. "adidas" or a representative's firm/individual name.
pageNoZero-based page index for pagination (default 0).
roleNoWhich EUIPO person register to search: "applicant" (default) or "representative".
sizeNoMax results per page (default 20).
_apiKeyNoOptional: your own EUIPO client_id:client_secret; Pipeworx supplies one if omitted.
countryNoISO 3166-1 alpha-2 country code to filter by, e.g. "DE", "US".

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",
-    "country": "DE",
-    "name": "adidas",
-    "role": "applicant"
-  }
-]New value: +[
+  {
+    "country": "DE",
+    "name": "adidas",
+    "role": "applicant"
+  }
+]
    • 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 read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely non-obvious context: rows carry a role and source, and address fields are deliberately withheld for individuals while business entities keep their registered address — a result-shape caveat an agent could not infer from annotations.

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 the core action, then the row-shape note, then the privacy caveat and example. Dense but every sentence contributes; the parenthetical role-value list is slightly verbose but useful for interpreting results.

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 seven optional parameters and no output schema, the description does the necessary work of describing what a returned row contains (role, source) and what is redacted (street/city/postal for individuals). Pagination defaults live in the schema, so nothing critical is missing, though it could note the zero-required-parameter behavior of an unfiltered search.

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 role enum and _apiKey fallback is already documented in the schema. The description reinforces role semantics via the quoted use case and example call but adds no syntax or format detail beyond that; baseline 3 applies.

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 — searching applicants or representatives on record with EUIPO for trademark/design procedures — and the quoted use case ("find the EUIPO representative record for a named law firm") pins down the exact intent. It is clearly distinguishable from siblings like euipo_search_trademarks or euipo_search_designs, which search different record types.

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 scenario and the role split (applicant vs. representative register) that determines when to use it, plus a full example call with filters. It stops short of explicit exclusions or naming which sibling to use when the user actually wants trademark documents rather than person records.

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