Skip to main content
Glama

NovaPixel LexGrid

ccnl_inquadramento_audit

Audits offered salary against official statutory tables for Italian National Collective Labor Agreements (CCNL Commercio, Metalmeccanica, Studi Professionali).

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)
numeroMensilitaNoAlias for monthsCount
livelloInquadramentoNoAlias for jobLevel
offeredMonthlySalaryEurNoOffered monthly base salary in EUR
seniorityIncrementsCountNoAccrued biennial seniority increments count
numeroScattiAnzianitaMaturatiNoAlias for seniorityIncrementsCount
retribuzioneMensileOffertaEurNoAlias for offeredMonthlySalaryEur

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and delivers little beyond purpose. It does add that comparison is against 'official statutory tables', which is meaningful behavioral context, but says nothing about what an audit produces (pass/fail, delta, warnings), what happens when offeredMonthlySalaryEur is omitted, or whether it is a pure read-only computation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the resource and scope front-loaded and zero filler. Nothing is redundant or hedged.

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 nine-parameter tool with no annotations and no output schema, the description covers only the top-level purpose. It leaves unclear which optional inputs are needed for a meaningful result, why three alias pairs exist for the same value, and what the audit returns — all gaps the description would need to fill.

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 all nine parameters, including the Italian aliases (livelloInquadramento, retribuzioneMensileOffertaEur, numeroScattiAnzianitaMaturati) and the 13/14 installment constraint. The description adds no additional parameter meaning, so the baseline of 3 applies.

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?

The description uses a specific verb ('Audits') with a specific resource ('offered salary against official statutory tables') and enumerates the covered agreements (CCNL Commercio, Metalmeccanica, Studi Professionali), which maps directly to the ccnlCode enum. It is clearly distinct from the sibling tools (cost calculation, fringe benefit optimization, gross-net simulation) without needing to name them, though it does not explicitly state the contrast.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the compliance-verification tool rather than a simulation tool, but there is no explicit when-to-use statement, no mention of prerequisites, and no guidance on when to prefer this over lordo_netto_irpef_simulator.

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