Skip to main content
Glama

cig_cup_anac_validator

Read-onlyIdempotent

[Deterministic public procurement validation. Pure calculation, read-only, side-effect free]. Validates Italian ANAC CIG (10-character alphanumeric checksum, Ordinary CIG and SmartCIG under D.Lgs 36/2023) and CUP (15-character public investment code) against official tender registry structure. Usage: Use this tool to verify public tender code validity. For tender threshold and publication deadline calculations, use 'bando_thresholds_calculator' instead. Returns: JSON object with { cig: { valid: boolean, type: 'ORDINARY' | 'SMART' | null, checksumOk: boolean }, cup: { valid: boolean, lengthOk: boolean }, isValid: boolean }.

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": "cig_cup_anac_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
cigNo10-character alphanumeric CIG code (e.g. 9876543210 or A012345678)
cupNo15-character alphanumeric CUP code (e.g. G12B23000010001)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's 'read-only, side-effect free' wording is somewhat redundant. However, it adds useful behavior beyond annotations: deterministic checksum validation, validation against official registry structure, and the specific return fields including 'type' and 'checksumOk'.

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?

The definition is front-loaded and organized into purpose, usage, and returns, with no irrelevant paragraphs. The bracketed preamble is mostly useful but repeats the read-only/idempotent traits already supplied by annotations.

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?

Because there is no output schema, the explicit return JSON shape is valuable and complete for a pure validation tool. One gap remains: required parameters are zero, yet the description does not state whether at least one of CIG or CUP must be supplied or what happens if neither is provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters already include length and examples, so the schema does most of the work. The description still adds meaning beyond the schema by identifying the CIG as a checksum-bearing code, distinguishing Ordinary CIG from SmartCIG, and clarifying that CUP is a public investment code.

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?

The description uses a specific verb, 'Validates', and names the exact resources: Italian ANAC CIG and CUP codes, including checksum and D.Lgs 36/2023 context. It also distinguishes the tool from 'bando_thresholds_calculator', so an agent can identify its scope 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?

It explicitly states when to use the tool ('verify public tender code validity') and routes threshold/deadline work to 'bando_thresholds_calculator' instead. This gives both a positive use case and a named exclusion.

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