Skip to main content
Glama

mdr_clinical_evaluation_screener

Read-onlyIdempotent

[MDR Article 61 clinical evaluation report (CER) & equivalence screener. Statutory audit, read-only, side-effect free]. Evaluates clinical evaluation sufficiency under Regulation (EU) 2017/745 Article 61 and Annex XIV, scoring literature search protocols, benefit-risk ratios, PMCF plans, and auditing Article 61(5) competitor access contracts. Usage: Pass clinical evaluation attributes and equivalence claims to audit sufficiency score before Notified Body submission. Returns: JSON object with { deviceName: string, overallSufficiencyScorePercent: number, statutoryVerdict: string, equivalenceAudit: object, literatureProtocolAudit: object, clinicalDataSufficiencyAudit: object, pmcfAudit: object, gapFindings: array, mandatoryNotifiedBodySubmissionItems: array }.

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>",
      "deviceRiskClass": "<deviceRiskClass>",
      "isImplantableDevice": "<isImplantableDevice>",
      "reliesOnClinicalEquivalenceToPredicate": "<reliesOnClinicalEquivalenceToPredicate>",
      "literatureSearchProtocolDefined": "<literatureSearchProtocolDefined>",
      "literatureAppraisalCriteriaDocumented": "<literatureAppraisalCriteriaDocumented>",
      "ownClinicalInvestigationConducted": "<ownClinicalInvestigationConducted>",
      "clinicalSafetyAndPerformanceEndpointsBenchmarked": "<clinicalSafetyAndPerformanceEndpointsBenchmarked>",
      "benefitRiskRatioAcceptable": "<benefitRiskRatioAcceptable>",
      "pmcfPlanFormulatedAnnexXivPartB": "<pmcfPlanFormulatedAnnexXivPartB>"
    },
    "name": "mdr_clinical_evaluation_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNameYesCommercial trade name of the medical device under evaluation
deviceRiskClassYesMDR Risk class of the device
isImplantableDeviceYesWhether device is implantable (triggers strict Article 61(4) clinical investigation rule)
benefitRiskRatioAcceptableYesWhether clinical evaluation concludes that risks are acceptable compared to clinical benefits
literatureSearchProtocolDefinedYesWhether a systematic literature search protocol (PICO, databases, search strings) is documented
pmcfPlanFormulatedAnnexXivPartBYesWhether a proactive Post-Market Clinical Follow-up (PMCF) Plan is established
lastLiteratureSearchCutoffDateIsoNoDate of most recent literature search cutoff (YYYY-MM-DD)
ownClinicalInvestigationConductedYesWhether pre-market clinical investigations were performed with the subject device
predicateDeviceAccessContractSignedNoArticle 61(5): For Class III/implantables, whether a contract with predicate manufacturer granting full technical doc access exists
literatureAppraisalCriteriaDocumentedYesWhether weighted data appraisal criteria (methodology, relevance) are specified (MDCG 2020-6)
reliesOnClinicalEquivalenceToPredicateYesWhether clinical evaluation relies on equivalence to a predicate device (Annex XIV 3)
clinicalSafetyAndPerformanceEndpointsBenchmarkedYesWhether clinical safety and performance endpoints are quantitatively benchmarked against state of the art

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the 'read-only, side-effect free' framing largely restates structured data. What the description adds beyond annotations is valuable: it discloses that the tool is a statutory audit/screening computation and specifies the full return payload, which matters because no output schema exists. It does not explain how scores are weighted or what verdict strings can be returned.

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?

It is front-loaded with the domain and statute, then segmented into Usage and Returns lines, so an agent can scan it quickly. The bracketed tag sentence is mildly redundant with the annotations, but the rest of the text is dense and purposeful.

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 12-parameter, 10-required statutory audit tool with no output schema, the description supplies the return object field-by-field, which is the most important gap to close. It remains slightly incomplete on interpretation — the scoring logic and the possible values of statutoryVerdict are not described, leaving the agent unable to anticipate verdict outcomes.

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% with 12 well-documented parameters including an enum for risk class, so the schema carries parameter meaning fully. The description only gestures at the inputs collectively ('clinical evaluation attributes and equivalence claims') without adding new semantics such as which flags trigger which statutory rule branches. Baseline 3 is appropriate.

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 precise verb and resource: it evaluates clinical evaluation sufficiency under MDR Article 61 / Annex XIV and audits Article 61(5) competitor access contracts. The enumerated audit targets (literature search protocols, benefit-risk ratios, PMCF plans, equivalence) make the scope unmistakable and clearly separable from the sibling MDR tools (classification engine, vigilance timeline calculator).

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?

The Usage line gives concrete context — pass clinical evaluation attributes and equivalence claims to obtain a sufficiency score before Notified Body submission — which tells the agent the workflow position. It stops short of explicit exclusions or naming an alternative sibling for adjacent questions (e.g., classification), so it is clear but not fully routing.

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