Skip to main content
Glama

NovaPixel LexGrid

subappalto_cascade_limiter

Audits subcontracting cascading limits under Art. 119 D.Lgs 36/2023, SIOS works prohibitions, non-rebate mandatory safety costs and CCNL equivalent worker protections.

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
livelloCascataNoAlias for cascadeLevel
categoriaLavoriNoAlias 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
ccnlContrattoPrincipaleNoAlias for mainContractCcnl
mandatorySafetyCostsEurNoMandatory non-rebate workplace safety costs in EUR
ccnlApplicatoSubappaltatoreNoAlias for subcontractorCcnl
costiSicurezzaSubappaltoEurNoAlias for mandatorySafetyCostsEur
ribassoApplicatoPercentualeNoAlias for discountPercentage
importoContrattoPrincipaleEurNoAlias for mainContractValueEur
importoSubappaltoRichiestoEurNoAlias for subcontractAmountEur

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden and only partly discharges it: it does disclose the substantive checks performed (cascade limits, SIOS non-scorporabilità, non-rebate safety costs, CCNL worker-equivalence), which is genuine behavioral content. It never says whether this is a read-only computation, whether it can fail/warn rather than return a result, or what the caller receives; missing annotations mean mutation-vs-read cannot be ruled out from structured fields alone.

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?

One front-loaded sentence with zero filler; the regulated scope appears before the list of audited dimensions. It is dense legal jargon in a single clause chain, which slightly hurts scannability, but nothing is redundant.

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

Completeness2/5

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

For a 16-parameter tool with no annotations and no output schema, the description is materially incomplete: nothing tells the agent what the audit returns, how violations are reported, or how to interpret a clean result versus a failed one. It also gives no hint about how the four Italian/English alias pairs should be reconciled, which matters when neither member is required.

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 parameter, including the Italian alias pairs, is documented in-schema, so the baseline is 3. The description only echoes the concepts already encoded in parameter descriptions (non-rebate safety costs, CCNL equivalence) without adding format rules, mutual-exclusivity of the alias pairs, or guidance on which of a duplicate parameter to populate.

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?

"Audits subcontracting cascading limits under Art. 119 D.Lgs 36/2023" gives a specific verb (audits) plus a precise regulatory scope, and the enumeration of SIOS prohibitions, safety costs and CCNL equivalence clearly separates it from the pricing/threshold/registry siblings. What it does not state is what an 'audit' produces — a verdict, a violation list, a boolean — so the agent knows the topic but not the outcome shape.

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 guidance, no preconditions (e.g. that a cascade level and both CCNLs should be supplied), and no reference to the sibling calculators for threshold or anomaly questions. The agent must infer from the legal topic alone whether this is the right tool for a given subcontracting question.

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