Skip to main content
Glama

abnormally_low_tender_eu_screener

Read-onlyIdempotent

[EU abnormally low tender statistical screener & labor dignity check. Deterministic calculation, read-only, side-effect free]. Detects abnormally low tender bids under Directive 2014/24/EU Article 69 using statistical median and standard deviation benchmarks, enforcing mandatory rejection for non-compliant labor costs or illegal state aid. Usage: Use this tool to audit submitted bids for price dumping anomalies and ensure compliance with mandatory collective bargaining minimum wages. Returns: JSON object with { tenderTitle: string, targetBidderName: string, statisticalMetrics: object, isSuspectedAbnormallyLow: boolean, laborCostDignityCheck: object, stateAidCompatibilityCheck: object, recommendedActionsForContractingAuthority: array }.

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": {
      "tenderTitle": "<tenderTitle>",
      "baseAuctionPriceEur": "<baseAuctionPriceEur>",
      "bids": "<bids>",
      "targetBidderName": "<targetBidderName>"
    },
    "name": "abnormally_low_tender_eu_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidsYesArray of all submitted bidder offers
tenderTitleYesPublic tender title or reference
targetBidderNameYesName of bidder being audited for abnormally low offer
baseAuctionPriceEurYesTender base auction price / maximum budget in EUR
hasStateAidAssistanceNoWhether the bidder received state aid subsidies ex Art. 107 TFEU
minimumStatutoryLaborCostEurNoMandatory statutory baseline labor cost stipulated in tender documents

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?

'Deterministic calculation, read-only, side-effect free' largely restates the readOnlyHint/idempotentHint annotations rather than adding to them. It does add real behavioral substance by noting that non-compliant labor costs or illegal state aid trigger mandatory rejection, which tells the agent the tool issues compliance conclusions rather than raw numbers, but permission requirements and threshold logic remain unstated.

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 purpose, then a compact Usage sentence and a Returns field map; nothing is padded. The bracketed preamble is slightly redundant with the annotations, but it is short and the rest of the text earns its place.

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 six parameters, no output schema, and nested bid objects, the description does the right work by enumerating the returned JSON keys (statisticalMetrics, isSuspectedAbnormallyLow, laborCostDignityCheck, recommendedActions). It stops short of explaining how statisticalMetrics are computed or what the numeric thresholds are, which would help an agent interpret borderline results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every field is documented in the schema, so the schema carries the burden. The description nonetheless clarifies the analytical role of the key inputs — bids benchmarked statistically against the base auction price, plus the labor-cost and state-aid checks that correspond to the optional parameters — beyond a bare field list.

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 (detects abnormally low tender bids) and anchors it to Directive 2014/24/EU Article 69 with the median/standard-deviation method, so the mechanism is clear. It does not differentiate itself from plausible siblings such as anomalia_offerte_calculator or de_minimis_state_aid_screener, leaving overlap for the agent to resolve.

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 explicit 'Usage:' line gives a clear context — auditing submitted bids for price dumping and checking collective-bargaining minimum wage compliance. There are no exclusions or named alternatives, so the agent knows when to use 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