Skip to main content
Glama

deviCERTS medical device regulatory data

Get the EU certificates of a device

get_device_certificates
Read-onlyIdempotent

List the EU notified-body certificates (from EUDAMED) of one device by slug: certificate number, type, legislation (MDR, IVDR, MDD, IVDD, AIMDD), notified body, issue and expiry dates, status (such as issued, supplemented, suspended, withdrawn) and whether EUDAMED still lists it. Use when the question is about CE certificates, notified bodies or certificate expiry of a known device. Do not use for FDA clearances or approvals (they are authorizations in get_device), for certificates by number, notified body or manufacturer (use search_certificates) or to find the device (use search_devices). 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_device_certificates"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesDevice slug: the last part of its https://devicerts.com/devices/<slug> URL, as returned by search_devices or find_device_by_identifier. A full page URL or a device:<slug> id is accepted. e.g. heartstart-frx-defibrillator-p180028

Output Schema

NameRequiredDescriptionDefault
idYes
noteYes
totalYes
deviceYes
formatYes
cite_asYes
certificatesYes
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 readOnly/idempotent annotations it discloses auth posture ('no login'), provenance (public EUDAMED and U.S. FDA records), sync cadence (monthly, weekly for EU certificates), cache staleness (up to 1 hour) and a rate limit (300 calls/minute per IP). It even points to get_data_sources for date semantics, so an agent knows how fresh and how costly the call is.

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 purpose, then usage, then exclusions, then operational facts — a logical order with no filler. Slight deduction because the long field enumeration in the first sentence largely duplicates what the existing output schema already conveys.

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?

For a single-parameter read tool with an output schema and full annotations, nothing an agent needs is missing: scope, trigger, three alternatives, data provenance, freshness, caching and rate limits are all stated.

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?

Only one parameter, and the schema already documents it fully (100% coverage, format, max length, accepted slug/id/URL forms, example). The description adds only 'by slug' and does not restate the accepted URL/device:<slug> forms, so it adds little beyond the schema — 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 ('List the EU notified-body certificates ... of one device by slug') and enumerates the returned fields (certificate number, type, legislation, notified body, dates, status, EUDAMED listing). This is clearly separable from get_device (FDA authorizations) and search_certificates (lookup by number/body/manufacturer).

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?

Gives an explicit trigger ('when the question is about CE certificates, notified bodies or certificate expiry of a known device') plus three named exclusions, each routed to a specific sibling: FDA clearances to get_device, lookups by number/body/manufacturer to search_certificates, device discovery to search_devices.

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.