Skip to main content
Glama

LexGrid European Public Tenders & TED eForms MCP

TED eForms Notice XML Schema & Regulation 2019/1780 Auditor

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. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the bracketed line 'Pure statutory calculation, read-only, side-effect free' largely restates them. The description does add value by enumerating the returned JSON keys (noticeType, isNoticeCompliant, euThresholdAudit, etc.), but it does not explain failure behavior, error shapes, or which threshold values are applied.

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 the purpose, then clearly separated Usage and Returns sections. The opening bracketed sentence is mildly redundant with the annotations but the rest is efficient and well ordered.

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 supplies the usage context and the full return object key list, which is exactly what an agent needs. Minor gaps remain around what constitutes non-compliance and threshold logic, but nothing critical is missing for correct invocation.

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 all 11 parameters documented and enums for noticeType, procedureType, buyerLegalType and contractNature, so the baseline is 3. The description mentions mandatory Business Terms and EU thresholds generically but never maps them to specific inputs such as buyerLegalType or estimatedTotalValueEur.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: audits public tender notice payloads against Regulation (EU) 2019/1780 eForms SDK standard forms, verifying mandatory Business Terms and EU thresholds. This is clearly distinct from classification tools like cpv_code_classifier_validator or threshold calculators, though it never names a sibling to route against explicitly.

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?

Gives an explicit usage context: pre-flight checking European public procurement contract notices prior to dispatch to the EU Publications Office. It does not state when NOT to use it or name an alternative tool, so it stops short of full routing 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