Skip to main content
Glama
Sign In
neroshooter

mcp-open-data-inpi

by neroshooter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rechercher des marques

rechercher_marques
Read-only

Search French, EU, and international trademarks in INPI by name, Nice class, holder, applicant, SIREN, status, and dates; returns a paginated list for follow-up detail.

Instructions

Recherche des marques françaises, de l'Union européenne et internationales dans la base de l'INPI, par nom, classe de Nice, titulaire, déposant, SIREN, statut et dates. Les critères se cumulent. Renvoie une liste paginée ; utilisez ensuite fiche_marque pour le détail.

Input Schema

NameRequiredDescriptionDefault
nomNoNom de la marque. Un mot seul trouve aussi les marques qui le contiennent comme mot (WORLDLINE trouve « WORLDLINE E-PAYMENT »). Plusieurs mots : recherche de l’expression exacte. Jokers : * (plusieurs caractères) et ? (un caractère).
sirenNoSIREN du déposant (marques françaises uniquement).
statutNoLibellé exact du statut. Marques FR : Demande publiée, Marque enregistrée, Marque renouvelée, Marque expirée, Demande totalement rejetée, Demande irrecevable après publication, Marque ayant fait l'objet d'une renonciation totale, Marque ayant fait l'objet d'un retrait total, Marque annulée, Marque déchue. Marques EU et WO (en anglais) : Registered, Application published, Application opposed, Application refused, Application withdrawn, Registration expired, Registration cancelled, Registration surrendered, Appeal pending.
tailleNoNombre de résultats par page (20 par défaut, 100 au plus).
classesNoClasses de Nice (1 à 45) : la marque doit viser au moins une de ces classes.
deposantNoNom du déposant d'origine.
depot_auNoDate de dépôt maximale (AAAA-MM-JJ).
depot_duNoDate de dépôt minimale (AAAA-MM-JJ).
originesNoOrigines à interroger : FR (française), EU (Union européenne), WO (internationale). Par défaut les trois.
positionNoRang du premier résultat (0 par défaut).
titulaireNoNom du titulaire (déposant ou titulaire actuel).
en_vigueurNoSi vrai, ne garde que les marques dont la date d'expiration n'est pas encore passée.
nom_contientNoFragment contenu dans le nom, même au milieu d’un mot (par exemple « WORLDL »).
requete_avanceeNoRequête au format INPI ajoutée aux autres critères avec ET, pour les besoins avancés. Exemple : [Mark=WORLDLINE] SAUF [ClassNumber=9]. Champs : Mark, NGram_Mark, ClassNumber, DEPOSANT, DEPOTIT, ApplicantIdentifier, Representative_LastName, ApplicationNumber, ApplicationDate, ExpiryDate, MarkCurrentStatusCode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description need not carry the full safety burden. It adds useful behavior: criteria are cumulative, and results are returned as a paginated list, with fiche_marque recommended for detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences with no waste. The primary search scope is front-loaded, followed by the cumulative-criteria behavior and the follow-up detail tool.

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 14-parameter search tool with 100% schema coverage, the description plus annotations and schema are enough to call it correctly. It states pagination and the fiche_marque handoff, though it does not describe returned fields or rate-limit behavior.

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 all 14 parameters are already documented in detail. The description summarizes the main criteria categories but adds little per-parameter meaning beyond what the schema provides.

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?

The description states a specific verb and resource: searching French, EU, and international trademarks in the INPI database. It also names supported criteria and explicitly routes detail requests to fiche_marque, distinguishing it from the detail sibling.

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?

It clearly indicates this tool is for searching and that fiche_marque should be used afterward for detail. It does not spell out when not to use it or compare it with the other recherche_* siblings, but the resource scope makes those alternatives clear.

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