Skip to main content
Glama

deviCERTS medical device regulatory data

Search EU certificates

search_certificates
Read-onlyIdempotent

Search EU notified-body certificates (EUDAMED) by certificate number, notified body number or name, holder name or SRN, legislation (MDR, IVDR), status and validity date, with offset paging. Returns up to 20 certificates per page: number, type, legislation, status, issue and expiry dates, notified body and holder with their DevicErts pages, plus total and next_offset. Use when a certificate number is known, or the question is which certificates a notified body issued or a manufacturer holds. Do not use for the certificates of one known device (use get_device_certificates) or for FDA clearances (use find_device_by_identifier). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_certificates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page, integer 1 to 20. Default 10.
numberNoCertificate number or its beginning, 2 to 60 characters; spaces are ignored. e.g. "2243595CE01", "EPT 0477". Default: none.
offsetNoNumber of results to skip, integer 0 to 999. Default 0. Pass next_offset from the previous page to get the next one; offset plus limit stays within the first 1000 results.
statusNoOnly certificates with this current EUDAMED status: issued, supplemented, amended, reissued, reinstated, restricted, suspended, cancelled or withdrawn. Default: all.
valid_onNoOnly certificates whose validity period (start to expiry) covers this date, YYYY-MM-DD. e.g. 2026-11-16. This checks dates only: a withdrawn or suspended certificate can match, so combine it with status. Default: any date.
legislationNoOnly certificates under this EU regulation: MDR (medical devices) or IVDR (in vitro diagnostics). Default: both.
manufacturerNoCertificate holder: words of its name (e.g. "Medtronic") or its EUDAMED SRN (e.g. IE-MF-000011725). Default: all.
notified_bodyNoNotified body: its four-digit number (e.g. 0344) or words of its name (e.g. "TÜV SÜD"). Default: all.
include_removedNotrue: also certificates EUDAMED no longer lists. Default false.

Output Schema

NameRequiredDescriptionDefault
totalYes
formatYes
offsetYes
cite_asYes
resultsYes
next_offsetYes
retrieved_atYes
status_as_ofYes
canonical_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses page size cap, returned fields including total and next_offset, data provenance and sync cadence, a 1-hour cache, and a 300 calls/minute rate limit. Those operational constraints are not derivable from the annotations or schema and materially affect how an agent should call and retry.

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?

Purpose is front-loaded, then return shape, then usage rules, then limits — a sensible order with no filler sentences. Minor redundancy: 'Read-only, no login' restates the readOnlyHint annotation, and the data-sync sentence overlaps what get_data_sources provides.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Nine optional parameters are fully covered by the schema, and the description still summarizes result fields, paging, and rate limits, which exceeds what this complexity requires. Nothing an agent needs to call it correctly or safely is missing.

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 enums and the offset/next_offset pattern is already documented, establishing a baseline of 3. The description's prose (number, notified body, holder/SRN, legislation, status, validity date, offset paging) paraphrases the schema without adding formats, matching rules, or defaults beyond it.

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?

Opens with a specific verb and resource ('Search EU notified-body certificates (EUDAMED)') and immediately enumerates the searchable dimensions. It distinguishes itself from get_device_certificates and find_device_by_identifier by name, so an agent can route without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the two triggering situations (a known certificate number, or 'which certificates a notified body issued or a manufacturer holds') and gives two named exclusions with the correct alternative for each. This is a complete when/when-not/alternative routing statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.