Moltline RegClock

Compute Deadlines

compute_deadlines

Read-onlyIdempotent

Compute every reporting deadline of one regime from the moment of awareness. FREE.

Typical input {"regime": "eu_nis2", "event_type": "significant_incident", "awareness_at": "2026-09-14T09:30:00+02:00"} returns {"deadlines": [{"obligation": "early_warning", "due_at": "2026-09-15T09:30+02:00", "citation": "Art. 23(4)(a)", ...}, ...]}. Later clocks that run from an earlier submission are estimated from that report's due time until you pass the actual time in submitted. DORA needs classification_at and a country for the bank-holiday rule; the SEC needs materiality_determined_at; HIPAA takes discovery_date and flags.individuals_affected. Use when an incident has just been identified and the agent needs the instants. Not for several regimes at once: use compute_deadlines_multi. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "flags must be an object"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input Schema

TableJSON Schema

Name	Required	Description
`flags`	No	condition answers: high_risk, processor, ongoing, handled_at, individuals_affected, max_residents_of_one_state, business_associate.
`regime`	Yes	regime id from list_regimes.
`subdiv`	No	optional subdivision code for the holiday calendar (e.g. BY for Bavaria).
`country`	No	ISO 3166-1 alpha-2 code for the public-holiday calendar (DORA weekend rule; SEC uses US).
`submitted`	No	actual submission times of earlier reports, e.g. {"initial_notification": "..."}.
`event_type`	No	event type within the regime; optional when the regime has one.
`awareness_at`	Yes	when the entity became aware, ISO 8601 with a UTC offset.
`entity_class`	No	e.g. trust_service_provider (NIS2), credit_institution / central_counterparty / trading_venue_operator / nis2_essential_or_important (DORA), business_associate (HIPAA).
`discovery_date`	No	HIPAA - the date the breach is treated as discovered (defaults to awareness date).
`classification_at`	No	DORA - when the incident was classified as major.
`measure_available_at`	No	CRA - when a corrective or mitigating measure became available.
`materiality_determined_at`	No	SEC - when the incident was determined to be material.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the readOnly and idempotent annotations by disclosing the 15-second delay on the free plan, no pagination, error return strings, estimation behavior for later clocks, and safe retry after correcting input. This is rich behavioral context that annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a clear purpose and includes a useful example, but it contains rambling and repetitive passages such as 'Typical output omits states in dry_run or disabled', 'Typical input shows a demonstration of the following...', and 'Also has a full breakdown of every event state.' These sentences add clutter without clear value, and 'FREE.' is ambiguous.

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?

Given the tool's complexity, the description is complete: it covers the typical use case, regime-specific parameter requirements, actual submission handling, error behavior, plan-based delays, retry safety, and sibling-tool routing. The presence of an output schema also means return-value details do not need to be fully spelled out.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful parameter context: DORA needs classification_at and country, SEC needs materiality_determined_at, HIPAA needs discovery_date and flags.individuals_affected, and the submitted object adjusts later deadline estimates. It does not describe every parameter in prose, but the schema already covers those individually.

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 specific verb and resource: compute every reporting deadline of one regime from the moment of awareness. It also differentiates itself from siblings by explicitly naming compute_deadlines_multi and deadline_status, so the agent can distinguish this tool clearly.

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?

The description gives explicit when-to-use guidance: use when an incident has just been identified and the agent needs the instants. It also gives exclusions with alternatives: not for several regimes at once (compute_deadlines_multi) and not for checking tomorrow's status (deadline_status).

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

All Moltline RegClock tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool targets a distinct stage of the incident-reporting workflow: classify_event qualifies the incident, compute_deadlines and compute_deadlines_multi produce deadlines, deadline_status monitors them, explain_rule cites the underlying rule, and timeline_export and validate_report handle output and pre-submission checks. No two tools are plausible substitutes; the single vs. multi-regime split between the two deadline tools is explicitly described.

Naming Consistency3/5

Most action tools follow a verb_noun pattern (classify_event, compute_deadlines, explain_rule, list_regimes, validate_report), but three tools use noun_noun or reversed forms (deadline_status, holiday_calendar, timeline_export). The convention is readable but not uniform, making it a mixed pattern rather than a consistent one.

Tool Count5/5

Nine tools is a well-scoped set for a regulatory deadline engine. Each tool maps to a necessary capability—discovery, classification, computation, status, explanation, calendar data, export, and validation—without redundant or filler entries.

Completeness5/5

The surface covers the full lifecycle: discover regimes, classify an incident, compute single or multi-regime deadlines, assess their status, inspect the statutory rule, export to calendar/CSV, and validate a draft report. Holiday and regime metadata tools fill supporting gaps, leaving no obvious dead-end for the stated purpose.

Resources

Need Help?