Skip to main content
Glama

mdr_device_classification_engine

Read-onlyIdempotent

[EU MDR Annex VIII medical device 22 classification rules engine. Pure statutory logic, read-only, side-effect free]. Determines medical device risk class (Class I, Is, Im, Ir, IIa, IIb, III) under Regulation (EU) 2017/745 Annex VIII based on invasiveness, duration, active functions, and anatomical site, specifying Notified Body conformity assessment routes. Usage: Pass device characteristics and intended purpose to obtain statutory classification, applicable Annexes, and PMS requirements. Returns: JSON object with { deviceName: string, riskClass: string, governingRule: string, notifiedBodyInterventionMandatory: boolean, conformityAssessmentRoutes: array, postMarketSurveillanceRequirement: string, summaryRationale: string }.

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": {
      "deviceName": "<deviceName>",
      "intendedPurpose": "<intendedPurpose>",
      "invasiveness": "<invasiveness>",
      "durationOfUse": "<durationOfUse>",
      "isActiveDevice": "<isActiveDevice>"
    },
    "name": "mdr_device_classification_engine"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNameYesCommercial or technical trade name of the medical device
invasivenessYesInvasiveness category ex Annex VIII Section 1
durationOfUseYesDuration of continuous use ex Annex VIII Section 1
isActiveDeviceYesWhether device relies on electrical energy or other power source
intendedPurposeYesClinical intended purpose as stated in instructions for use and labeling
activeDeviceFunctionNoFunctional category for active devices ex Rules 9-12
hasMeasuringFunctionNoWhether device has a statutory measuring function (Class Im)
utilizesNanomaterialsNoRule 19: Whether device consists of or incorporates nanomaterial with exposure potential
absorbedByHumanBodyLocallyNoRule 21: Whether device is composed of substances intended to be absorbed or dispersed
isSterileWhenPlacedOnMarketNoWhether device is delivered sterile (Class Is)
isReusableSurgicalInstrumentNoWhether device is a reusable surgical instrument (Class Ir)
softwareInformsCriticalPatientManagementNoRule 11: Whether software decisions could cause death or irreversible deterioration
incorporatesMedicinalSubstanceAsAncillaryNoRule 14: Whether device incorporates a substance which is a medicinal product if used separately

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and idempotentHint, and the 'Pure statutory logic, read-only, side-effect free' preface largely restates them, so that earns little. The genuinely additive part is the Returns block describing the output object, but it omits behavioral caveats such as how conflicting rules are resolved, treatment of borderline/combination devices, or any disclaimer that this is not a legal determination.

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?

The definition is front-loaded with the statutory basis in a bracketed preface, then split cleanly into Usage and Returns sections. Every line carries informational weight and there is no filler or repetition beyond the short safety restatement.

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 13 parameters and no output schema, the description usefully compensates by spelling out the returned JSON fields (riskClass, governingRule, notifiedBodyInterventionMandatory, routes, PMS requirement). What remains thin is edge-case handling for devices spanning multiple Annex VIII rules, which for a statutory classifier is a meaningful but not fatal gap.

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 the schema already carries parameter meaning and the baseline is 3. The description only generically recaps the drivers ('invasiveness, duration, active functions, and anatomical site'), and notably references anatomical site even though no such parameter exists in the schema, which mildly risks sending the agent looking for a field that is not there.

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 names a specific verb and resource ('Determines medical device risk class ... under Regulation (EU) 2017/745 Annex VIII') and enumerates the exact output classes (Class I, Is, Im, Ir, IIa, IIb, III). That is far more specific than its siblings like mdr_clinical_evaluation_screener or mdr_vigilance_reporting_timeline_calculator, so an agent can route confidently without opening any schema.

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

Usage Guidelines3/5

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

A 'Usage:' line tells the agent what to pass and what it will get back, giving an implied context for use. However, it never states when NOT to use it, nor does it point to an alternative for adjacent questions (clinical evidence, vigilance timelines, IVDR classification), so the routing guidance stops short of explicit alternatives.

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.

Resources