Skip to main content
Glama

bando_thresholds_calculator

Read-onlyIdempotent

[Deterministic public procurement calculator. Pure calculation, read-only, side-effect free]. Calculates EU tender thresholds under D.Lgs 36/2023, direct award limits (Art. 50), mandatory publication windows in days, electronic submission time reductions, and cumulative ISO provisional guarantee discounts. Usage: Use this tool for public tender procedure planning, statutory deadlines, and guarantee calculation. For subcontracting limits, use 'subappalto_cascade_limiter'. For lowest-price anomaly trimming, use 'anomalia_offerte_calculator'. Returns: JSON object with { isAboveEuThreshold: boolean, applicableProcedure: string, minimumPublicationDays: number, provisionalGuarantee: { basePercentage: number, discountedPercentage: number, requiredEur: number }, statutoryReferences: string[] }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bando_thresholds_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
settoreNoItalian alias for procurementSector
totalAmountEurNoTotal estimated tender base value in EUR excluding VAT
urgentProcedureNoWhether urgent procedure is declared under statutory justification
proceduraUrgenteNoItalian alias for urgentProcedure
procurementSectorNoProcurement sector category
modalitaTelematicaNoItalian alias for electronicSubmission
stazioneAppaltanteNoItalian alias for contractingAuthorityType
electronicSubmissionNoWhether electronic submission is enabled (reduces mandatory deadlines)
certificazioniQualitaNoItalian alias for qualityCertifications
importoComplessivoEurNoItalian alias for totalAmountEur
qualityCertificationsNoBidder quality certifications for provisional guarantee reductions
contractingAuthorityTypeNoType of contracting authority

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 safety is covered; the description still adds real value by asserting the tool is deterministic and side-effect free, and by pinning the statutory basis (D.Lgs 36/2023, Art. 50). The stated return shape also tells the agent this produces a single computed verdict rather than a list. It stops short of describing edge-case behavior, e.g. what happens with mixed or missing sector input.

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 front-loaded bracketed qualifier plus labeled 'Usage' and 'Returns' sections make it easy to scan, and no sentence is filler. It is somewhat dense, packing five distinct calculations and a full return signature into a short block, but the structure carries that load well.

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, yet the description supplies the complete return contract inline (isAboveEuThreshold, applicableProcedure, minimumPublicationDays, provisionalGuarantee breakdown, statutoryReferences). Combined with 100% parameter coverage in the schema and annotations covering the safety profile, an agent has everything needed to call this correctly.

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 property, including all Italian aliases, is documented in the schema itself, so the baseline of 3 applies. The description mentions the concepts the inputs feed (thresholds, publication days, certification discounts) but adds no syntax, unit, or alias-precedence detail beyond the schema; notably it never explains that the parameters come in Italian/English alias pairs or how conflicting aliases resolve.

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 plus a precise set of resources: EU tender thresholds under D.Lgs 36/2023, direct award limits under Art. 50, publication windows, electronic submission reductions, and ISO guarantee discounts. It also states the domain (Italian public procurement) and that the tool is a pure calculator, which is enough to distinguish it from the sibling calculators without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit use case (tender procedure planning, statutory deadlines, guarantee calculation) and then routes the agent away from itself twice: subcontracting limits go to 'subappalto_cascade_limiter', lowest-price anomaly trimming goes to 'anomalia_offerte_calculator'. That is exactly the when-to-use / when-not-to-use pattern.

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