Skip to main content
Glama

NovaPixel LexGrid

cig_cup_anac_validator

Validates Italian ANAC CIG (10-char modulo checksum, Ordinary CIG and SmartCIG) and CUP (15-char public project code) against public tender registry guidelines.

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
cupNo15-character alphanumeric CUP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the validation rules applied (modulo checksum, Ordinary CIG vs SmartCIG, 15-char CUP) and that checks run against public tender registry guidelines, which is real behavioral context. However, it never says what the tool returns (per-code validity? error strings?), whether it is a pure local check or a remote registry lookup, or what happens when a code fails.

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 dense sentence, front-loaded with the verb and the resources, with the code formats inline. Nothing is padded or repeated.

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

Completeness3/5

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

No annotations and no output schema mean the description must cover return behavior, and it does not — an agent cannot tell whether it gets a boolean, a list of violations, or a normalized code back. The supported code families are covered, but for a validator with zero structured behavioral metadata this leaves a meaningful hole.

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% and both properties already document their format and length, so the baseline is 3. The description adds the checksum algorithm and the Ordinary/SmartCIG distinction, which is genuine meaning beyond the schema, but it leaves open whether either parameter alone is valid input (both are optional) and whether checks are performed independently.

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 (validates) applied to two named resources (CIG, CUP) and pins down their nature: 10-char modulo-checksum ANAC code with Ordinary CIG and SmartCIG variants, and a 15-char public project code. The sibling tools are calculators/limiters, so the scope is clearly distinct from anything that computes thresholds or cascades.

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 tool to call when it needs to check CIG/CUP well-formedness before some downstream step. There is no explicit statement of when to use it versus not, no prerequisites, and no mention of what to do with the result.

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