Skip to main content
Glama

ccnl_inquadramento_audit

Read-onlyIdempotent

[Deterministic Italian labour agreement audit. Pure calculation, read-only, side-effect free]. Audits proposed salary against official statutory minimum wage tables (paga base, contingenza, terzo elemento, EDR) for national collective bargaining agreements (CCNL Commercio & Terziario Confcommercio, CCNL Metalmeccanica Industria Federmeccanica, CCNL Studi Professionali Confprofessioni). Evaluates job classification level and statutory biennial seniority increments (scatti di anzianità). Usage: Use this tool to audit whether an employment contract complies with mandatory minimum wage levels under Italian law. Do NOT use for IRPEF tax deductions (use 'lordo_netto_irpef_simulator'). Returns: JSON object with { ccnlCode: string, jobLevel: string, statutoryMinimumMonthlyEur: number, offeredMonthlyEur: number, isCompliant: boolean, gapMonthlyEur: number, accruedSeniorityEur: number, legalBasis: string }.

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": {
      "ccnlCode": "<ccnlCode>"
    },
    "name": "ccnl_inquadramento_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccnlCodeYesNational collective labor agreement code
jobLevelNoJob level (e.g. 1, 2, 3, 4, 5, B1, C1, D1)
monthsCountNoNumber of annual salary installments (13 or 14)
numeroMensilitaNoItalian alias for monthsCount (13 or 14)
livelloInquadramentoNoItalian alias for jobLevel
offeredMonthlySalaryEurNoOffered monthly base salary in EUR excluding bonuses
seniorityIncrementsCountNoAccrued biennial seniority increments count (scatti di anzianita)
numeroScattiAnzianitaMaturatiNoItalian alias for seniorityIncrementsCount
retribuzioneMensileOffertaEurNoItalian alias for offeredMonthlySalaryEur

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with "pure calculation, read-only, side-effect free" and "deterministic", which is partly repetition but adds the determinism guarantee. It also discloses the basis of computation (official statutory tables, job level, biennial scatti) and the legalBasis output field, though it says nothing about failure modes for an unrecognized level/agreement combination.

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 bracket summary followed by Usage and Returns sections is easy to scan, and the alternative tool is named before the return fields. Minor waste from restating read-only/side-effect-free information already carried by annotations, but nothing is buried or bloated.

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 no output schema, the description compensates by enumerating the return JSON fields (ccnlCode, statutoryMinimumMonthlyEur, isCompliant, gapMonthlyEur, accruedSeniorityEur, legalBasis), so the agent knows what it gets back. For a 9-parameter tool the only gap is that alias precedence between English and Italian parameters is never addressed.

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 baseline of 3 applies; the schema already documents ccnlCode, jobLevel, monthsCount and the Italian aliases. The description adds the domain meaning of the evaluation inputs (classification level, statutory biennial scatti) but does not clarify how the duplicated English/Italian alias pairs interact, which is the one genuinely ambiguous part of the parameter set.

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 a proposed salary against statutory minimum wage tables for three named CCNL agreements, and enumerates the pay components (paga base, contingenza, terzo elemento, EDR) plus seniority increments it evaluates. An agent can distinguish this from the payroll/tax siblings without opening the 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?

Explicit when-to-use ("audit whether an employment contract complies with mandatory minimum wage levels under Italian law") and an explicit exclusion with the correct alternative ("Do NOT use for IRPEF tax deductions (use 'lordo_netto_irpef_simulator')"). Both the positive and negative routing conditions are stated.

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