Skip to main content
Glama

mdr_vigilance_reporting_timeline_calculator

Read-onlyIdempotent

[EU MDR Article 87 vigilance incident reporting statutory deadlines calculator. Pure calculation, read-only, side-effect free]. Calculates strict statutory notification deadlines under Regulation (EU) 2017/745 Article 87 (public health threat: 2 days; death/deterioration: 10 days; serious incidents: 15 days) and prepares initial MIR vigilance report payloads. Usage: Pass incident awareness date and severity classification to compute exact deadline dates and EUDAMED notification requirements. Returns: JSON object with { incidentReferenceId: string, incidentSeverityType: string, statutoryDeadlineDays: number, dateOfIncidentAwarenessIso: string, statutoryDeadlineDateIso: string, isImmediateNotificationMandatory: boolean, eudamedReportingFormType: string, initialReportRequiredContent: object }.

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": {
      "incidentReferenceId": "<incidentReferenceId>",
      "deviceName": "<deviceName>",
      "manufacturerName": "<manufacturerName>",
      "dateOfIncidentAwarenessIso": "<dateOfIncidentAwarenessIso>",
      "incidentSeverityType": "<incidentSeverityType>",
      "isDeviceCausalRelationshipEstablishedOrSuspected": "<isDeviceCausalRelationshipEstablishedOrSuspected>",
      "isFieldSafetyCorrectiveActionPlanned": "<isFieldSafetyCorrectiveActionPlanned>",
      "reportingToMemberStateCompetentAuthorityIso2": "<reportingToMemberStateCompetentAuthorityIso2>"
    },
    "name": "mdr_vigilance_reporting_timeline_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNameYesCommercial name and model of the medical device involved
manufacturerNameYesLegal name of the manufacturer or EU Authorized Representative
incidentReferenceIdYesInternal complaint or vigilance file reference identifier
incidentSeverityTypeYesIncident severity category ex MDR Article 87(3)-(5)
dateOfIncidentAwarenessIsoYesDate when manufacturer first became aware of the incident (YYYY-MM-DD)
isFieldSafetyCorrectiveActionPlannedYesWhether a Field Safety Corrective Action (FSCA) and Field Safety Notice (FSN) are being initiated (Art. 87(8))
reportingToMemberStateCompetentAuthorityIso2Yes2-letter ISO country code of national competent authority receiving notification
isDeviceCausalRelationshipEstablishedOrSuspectedYesWhether a causal link between device and incident is established or reasonably possible

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, and the phrase 'Pure calculation, read-only, side-effect free' largely restates that rather than extending it. The description does add genuinely new behavior context — that it also prepares initial MIR vigilance report payloads and returns a structured decision object — but it says nothing about how deadlines are counted (calendar vs business days), timezone/ISO handling, or what happens for the TREND_REPORTABLE_INCIDENT category, which is the most error-prone aspect.

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?

Three clearly labeled segments (purpose bracket, Usage, Returns) with the core purpose front-loaded and no filler prose. The only waste is the bracketed 'Pure calculation, read-only, side-effect free' clause, which duplicates what the annotations already declare.

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 eight required parameters, no output schema, and heavy regulatory framing, the explicit Returns field list is valuable and largely closes the return-value gap. The definition is almost self-sufficient; only the trend-reportable case and the effect of the FSCA/causality booleans on the outcome are left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the enum: it maps severity classes to statutory day counts (public health threat 2, death/deterioration 10, serious incidents 15), which the schema itself does not state. The gaps are that TREND_REPORTABLE_INCIDENT is in the enum but has no stated deadline, and the two boolean parameters (causal relationship, FSCA planned) are never explained in terms of their effect on the computed result.

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 (calculates) and resource (MDR Article 87 statutory notification deadlines), plus concrete deadline values (2/10/15 days) that make the scope unmistakable. An agent can tell this apart from the sibling MDR screener/classifier tools or the generic deadline calculators purely from the description.

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?

The 'Usage' line tells the agent what to pass (incident awareness date and severity classification) to get deadline dates and EUDAMED notification requirements, which is operational guidance but not when-to-use versus when-not-to-use. No exclusions, prerequisites, or named alternatives are given, so the agent must infer the boundary with tools like mdr_device_classification_engine or eu_tender_deadlines_calculator from the domain alone.

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