Skip to main content
Glama

ted_eforms_notice_validator

Read-onlyIdempotent

[TED eForms notice XML schema & Regulation 2019/1780 auditor. Pure statutory calculation, read-only, side-effect free]. Audits public tender notice payloads against Commission Implementing Regulation (EU) 2019/1780 eForms SDK standard forms, verifying mandatory Business Terms (BT) and EU thresholds. Usage: Use this tool to pre-flight check European public procurement contract notices prior to dispatch to the EU Publications Office. Returns: JSON object with { noticeType: string, isNoticeCompliant: boolean, eformsNoticeSubType: string, euThresholdAudit: object, businessRulesValidation: object, deadlineAudit: 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": {
      "noticeType": "<noticeType>",
      "buyerLegalType": "<buyerLegalType>",
      "procedureType": "<procedureType>",
      "estimatedTotalValueEur": "<estimatedTotalValueEur>",
      "mainCpvCode": "<mainCpvCode>",
      "contractNature": "<contractNature>"
    },
    "name": "ted_eforms_notice_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotsCountNoNumber of lots if divided
noticeTypeYeseForms standard notice sub-type
mainCpvCodeYesMain CPV classification code (e.g. 72220000-1)
procedureTypeYesTendering procedure ex Directive 2014/24/EU
buyerLegalTypeYesLegal nature of the contracting authority
contractNatureYesNature of the public contract
dispatchDateIsoNoNotice dispatch date to EU Publications Office (YYYY-MM-DD)
hasLotsDivisionNoWhether the contract is divided into lots ex Art. 46
isEuFundedProjectNoWhether the project is financed by European Union funds
submissionDeadlineIsoNoTender submission deadline date (YYYY-MM-DD)
estimatedTotalValueEurYesEstimated contract value excluding VAT in EUR

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 'read-only, side-effect free' largely restates them, but 'pure statutory calculation' adds that results are deterministic and derived from regulation rather than data lookup. With no output schema present, the enumerated return keys (noticeType, isNoticeCompliant, euThresholdAudit, businessRulesValidation, deadlineAudit) supply genuinely useful disclosure that annotations cannot.

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?

Front-loaded with a bracketed scope tag, then Usage, then Returns, so an agent can stop reading at any level. Minor waste: 'read-only, side-effect free' repeats the annotations and the regulation citation appears twice.

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 an 11-parameter validator with no output schema, the description covers scope, timing, and return shape, which is most of what is needed. One ambiguity remains: it frames the input as 'notice XML' payloads while the schema takes a flat object of eForms fields, leaving an agent unsure whether raw XML or structured fields are expected.

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 four enums, so the schema already carries parameter meaning. The description adds only indirect hints, such as EU threshold checking implying the role of estimatedTotalValueEur and buyerLegalType (BT verification), without explaining any individual parameter.

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 and resource: auditing public tender notice payloads against Regulation (EU) 2019/1780 eForms, verifying mandatory Business Terms and EU thresholds. That scope is concrete enough to separate it from sibling validators such as cpv_code_classifier_validator or cig_cup_anac_validator 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 Guidelines4/5

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

The 'Usage' line gives a clear trigger: pre-flight check of European public procurement contract notices before dispatch to the EU Publications Office. It does not state exclusions or name any alternative, so an agent knows when to call it but not when to prefer something else.

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