Skip to main content
Glama

espd_dgue_eligibility_screener

Read-onlyIdempotent

[ESPD / DGUE European exclusion grounds & self-cleaning screener. Pure statutory calculation, read-only, side-effect free]. Audits economic operator eligibility under Directive 2014/24/EU Article 57, checking mandatory exclusion grounds, discretionary misconduct, and Article 57(6) self-cleaning measures. Usage: Use this tool to verify bidder compliance with ESPD/DGUE declaration requirements and evaluate whether self-cleaning rehabilitation measures are legally sufficient. Returns: JSON object with { operatorName: string, isEligibleToParticipate: boolean, verdictStatus: string, mandatoryBreachesFound: array, selfCleaningAudit: object, economicCapacityAudit: 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": {
      "operatorName": "<operatorName>",
      "countryIso2": "<countryIso2>",
      "mandatoryExclusionChecks": "<mandatoryExclusionChecks>"
    },
    "name": "espd_dgue_eligibility_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryIso2YesCountry of establishment (2-letter ISO code)
operatorNameYesEconomic operator legal business name
mandatoryExclusionChecksYesMandatory statutory exclusion criteria checklist ex Art. 57(1)-(2)
economicFinancialStandingNoEconomic and financial standing assessment ex Art. 58(3)
discretionaryExclusionChecksNoDiscretionary statutory exclusion criteria checklist ex Art. 57(4)
selfCleaningMeasuresExArt57_6NoSelf-cleaning remediation package ex Art. 57(6)

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=true and idempotentHint=true, so the description's 'read-only, side-effect free' phrasing is largely redundant. It does add genuinely new context, though: the tool is a 'pure statutory calculation' with no external lookups, meaning results are deterministic inputs-in/verdict-out. It omits what happens when the optional discretionary or financial-standing blocks are left out.

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 short, well-structured sentences: a bracketed scope tag, Usage, and Returns, so the reader is front-loaded with scope before mechanics. The 'read-only, side-effect free' clause duplicates the annotation hints and is the one non-earning phrase.

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 no output schema, the Returns line is essential and it does enumerate the key fields (verdictStatus, mandatoryBreachesFound, selfCleaningAudit, economicCapacityAudit). For a six-parameter, deeply nested legal classifier it is nearly sufficient, though it leaves the possible verdictStatus values and the effect of omitting the optional blocks unspecified.

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 every nested field already carries its statutory citation (e.g. 'ex Art. 57(1)(b)'), so the schema does the heavy lifting. The description adds no syntax, format, or optionality guidance beyond what is structured (for example, it never mentions that discretionaryExclusionChecks and economicFinancialStanding are optional). 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?

States a specific verb and resource: audits economic operator eligibility under Directive 2014/24/EU Article 57, covering mandatory exclusion grounds, discretionary misconduct, and Article 57(6) self-cleaning. This is clearly distinguishable from sibling screeners such as abnormally_low_tender_eu_screener, which address a different procurement stage.

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: verify bidder compliance with ESPD/DGUE declaration requirements and evaluate whether self-cleaning rehabilitation is legally sufficient. It does not, however, state when not to use it or name any alternative/companion tool, so the agent must infer routing to siblings on its own.

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