Skip to main content
Glama

NovaPixel LexGrid

bando_thresholds_calculator

Calculates EU tender thresholds under D.Lgs 36/2023, direct award limits, mandatory publication windows in days, electronic submission reductions and ISO provisional guarantee discounts.

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
settoreNoAlias for procurementSector
totalAmountEurNoTotal estimated tender base value in EUR excluding VAT
urgentProcedureNoWhether urgent procedure is declared
proceduraUrgenteNoAlias for urgentProcedure
procurementSectorNoProcurement sector category
modalitaTelematicaNoAlias for electronicSubmission
stazioneAppaltanteNoAlias for contractingAuthorityType
electronicSubmissionNoWhether electronic submission is enabled (default true)
certificazioniQualitaNoAlias for qualityCertifications
importoComplessivoEurNoAlias for totalAmountEur
qualityCertificationsNoBidder quality certifications for guarantee discounts
contractingAuthorityTypeNoType of contracting authority

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Calculates' plus enumerated numeric outputs implies a pure, side-effect-free computation, but the description never explicitly states it is read-only, deterministic, or that it returns figures rather than performing a filing. All parameters are optional (0 required), yet the description gives no hint about what happens when inputs are omitted or which defaults apply.

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?

A single front-loaded sentence with no filler; the regulatory reference and the enumerated outputs both earn their place. It is dense but well ordered, moving from the primary computation to the secondary adjustments.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter tool with no output schema and no annotations, the definition outlines the categories of results but omits how sector and authority type select the threshold table, how defaults behave, and whether output is a structured breakdown or a summary figure. Adequate as a starting point, not sufficient to invoke confidently without opening the schema.

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%, so the schema already documents every field including the Italian aliases. The description adds modest conceptual linkage — 'electronic submission reductions' to electronicSubmission, 'ISO provisional guarantee discounts' to qualityCertifications — but says nothing about the alias pairs or the sector/authority enums that drive the threshold tables.

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 ('Calculates') and a specific resource domain ('EU tender thresholds under D.Lgs 36/2023'), then enumerates the derived outputs (direct award limits, publication windows, electronic submission reductions, ISO guarantee discounts). This is clearly distinguishable from the anomaly-score and cascade-limit siblings, though it never names an alternative.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no statement of prerequisites, and no routing to a sibling such as anomalia_offerte_calculator. The agent must infer from the sentence alone that this is a pre-award threshold lookup rather than a bid evaluation.

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