Skip to main content
Glama

eu_tender_deadlines_calculator

Read-onlyIdempotent

[EU public tender statutory minimum deadlines calculator. Deterministic calculation, read-only, side-effect free]. Calculates statutory publication and bid submission deadlines under Directive 2014/24/EU Articles 27-31, factoring in electronic reductions, PIN notices, urgency, and Regulation 1182/71 weekend rollovers. Usage: Use this tool to ensure public procurement schedules comply strictly with EU statutory minimum calendar day requirements. Returns: JSON object with { dispatchDateIso: string, procedureType: string, statutoryBaseDays: number, reductionsApplied: object, netMandatoryCalendarDays: number, calculatedExpiryDateIso: string, finalAdjustedExpiryDateIso: string, weekendRolloverApplied: boolean }.

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": {
      "dispatchDateIso": "<dispatchDateIso>",
      "procedureType": "<procedureType>"
    },
    "name": "eu_tender_deadlines_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
procedureTypeYesProcurement procedure category
dispatchDateIsoYesNotice dispatch date in ISO format (YYYY-MM-DD)
isUrgencyStateJustifiedNoWhether duly substantiated urgency renders standard deadlines impracticable ex Art. 27(4) (shortens deadline to 15 days)
isElectronicSubmissionOfferedNoWhether electronic submission of tenders is offered (-5 days discount ex Art. 27(2), default: true)
isPriorInformationNoticePinPublishedNoWhether a PIN notice was published between 35 days and 12 months prior (shortens deadline to 15 days)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 description largely restates them as 'read-only, side-effect free', though 'deterministic' adds a genuine trait. It also usefully spells out the return payload. For a stateless calculator there is little else to disclose, but the description adds only modest value beyond the structured fields.

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?

The definition is front-loaded and broken into labelled Usage and Returns blocks, which is easy to scan. The bracketed lead sentence partially restates the tool name and the read-only claim, so a small amount of redundancy remains.

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?

There is no output schema, but the description enumerates the returned JSON fields, and all five inputs are documented in the schema. Legal basis, determinism, and return shape are all covered, which is complete for a pure calculation tool.

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% and the schema already explains every parameter with legal citations, including the -5 day electronic discount and the 15 day urgency/PIN shortcuts. The description's mention of 'electronic reductions, PIN notices, urgency' only echoes those names without new semantics, so 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?

The description names a specific verb and resource — calculating statutory publication and bid submission deadlines — and anchors it to Directive 2014/24/EU Articles 27-31, plus Regulation 1182/71 rollovers. That is far more precise than a generic 'calculator' and distinguishes it from the neighbouring threshold, incentive, and timeline calculators.

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 states the condition clearly: use it to make public procurement schedules comply with EU statutory minimum calendar day requirements. It gives no explicit exclusions or named alternatives (e.g. national deadline rules or non-EU regimes), so it stops short of full when/when-not guidance.

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