Skip to main content
Glama

subappalto_cascade_limiter

Read-onlyIdempotent

[Deterministic public procurement audit. Pure calculation, read-only, side-effect free]. Audits subcontracting cascading limits under Art. 119 D.Lgs 36/2023, SIOS specialized works prohibitions, non-rebate workplace safety costs, and mandatory CCNL equivalent worker protections. Usage: Use this tool to verify whether a subcontracting request is legally permissible under Italian public tender rules. Returns: JSON object with { isPermissible: boolean, maxCascadeAllowed: number, safetyCostsProtected: boolean, ccnlEquivalenceRequired: boolean, violations: 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": "subappalto_cascade_limiter"
  }
}

Input Schema

NameRequiredDescriptionDefault
cascadeLevelNoCascade level: 1 = direct subcontractor, 2 = sub-subcontractor
workCategoryNoWork category classification
livelloCascataNoItalian alias for cascadeLevel
categoriaLavoriNoItalian alias for workCategory
mainContractCcnlNoLabor collective agreement prescribed by main tender
subcontractorCcnlNoLabor collective agreement applied by subcontractor
discountPercentageNoTender discount / rebate percentage applied
mainContractValueEurNoTotal main contract value in EUR
subcontractAmountEurNoRequested subcontract amount in EUR
ccnlContrattoPrincipaleNoItalian alias for mainContractCcnl
mandatorySafetyCostsEurNoMandatory non-rebate workplace safety costs in EUR
ccnlApplicatoSubappaltatoreNoItalian alias for subcontractorCcnl
costiSicurezzaSubappaltoEurNoItalian alias for mandatorySafetyCostsEur
ribassoApplicatoPercentualeNoItalian alias for discountPercentage
importoContrattoPrincipaleEurNoItalian alias for mainContractValueEur
importoSubappaltoRichiestoEurNoItalian alias for subcontractAmountEur

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description restates the annotation profile (read-only, side-effect free) but adds two things annotations cannot convey: the audit is deterministic/pure-calculation, and the exact return shape with five named fields. Since no output schema exists, the inline 'Returns' contract is genuinely load-bearing information.

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 a bracketed trait block, then dedicated Usage and Returns lines — easy to scan and appropriately short. The bracketed preamble partly duplicates the audit sentence (deterministic/read-only/pure calculation), which is minor waste.

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 a 16-parameter, zero-required audit tool with no output schema, the definition supplies both the decision question and the response contract, which is close to sufficient. The remaining gaps are the alias-pair behavior and how missing optional inputs (e.g. no contract value) affect the result.

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 coverage is 100%, so every one of the 16 parameters is already documented, and the description adds only the high-level concern areas rather than parameter-level meaning. It notably does not explain that cascadeLevel/workCategory and their Italian counterparts are aliases of each other, which is the main semantic risk in this schema.

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 subcontracting cascading limits') and enumerates the exact legal checks performed (Art. 119 D.Lgs 36/2023, SIOS prohibitions, non-rebate safety costs, CCNL equivalence). The domain is narrow enough that an agent can distinguish it from the threshold, offer-anomaly, and CIG/CUP siblings without opening any schema.

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 condition: verify whether a subcontracting request is legally permissible under Italian public tender rules. It does not state when-not to use it or name the sibling calculators as alternatives, so routing is implied rather than explicit.

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