Skip to main content
Glama

cpv_code_classifier_validator

Read-onlyIdempotent

[Universal CPV code classifier & Modulo 11 check-digit validator. Pure statutory calculation, read-only, side-effect free]. Validates and classifies public procurement supplies, works, and services against Regulation (EC) No 213/2008 CPV 8+1 digit codes with Modulo 11 check-digit verification. Usage: Use this tool to validate CPV codes in tender documents or resolve division, group, and category hierarchies. Returns: JSON object with { queriedCodeOrKeyword: string, isValidCpvFormat: boolean, isCheckDigitValid: boolean, cleanCpvCode: string, hierarchy: object, descriptions: object }.

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": {
      "cpvCodeOrKeyword": "<cpvCodeOrKeyword>"
    },
    "name": "cpv_code_classifier_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvCodeOrKeywordYes8-digit or 9-digit CPV code (e.g. 72220000-1 or 72220000) or sector keyword
supplementaryCodeNoOptional alphanumeric supplementary CPV code (e.g. AA01-1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 statutory calculation, side-effect free' while adding the statutory basis (Reg. 213/2008) and the Modulo 11 rule. It goes beyond the annotations by disclosing the deterministic legal authority behind the result, though it does not discuss failure modes or edge cases.

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 bracketed summary, then labelled 'Usage:' and 'Returns:' blocks make it easy to scan and front-load the core purpose. Slight redundancy between the header sentence and the body costs it the top mark, but nothing is wasted.

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 returned JSON fields (validity flags, cleanCpvCode, hierarchy, descriptions), which is what an agent needs to interpret results. The deeper structure of the 'hierarchy' and 'descriptions' objects is left unexplained, keeping it just below fully complete.

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 both parameters (the 8/9-digit code or keyword, and the optional supplementary code) are already documented in the schema. The description restates the 8+1 digit format but adds no format rules, accepted keyword syntax, or supplementary-code semantics beyond what the schema provides, so baseline 3 applies.

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 names a specific verb+resource pair: it 'validates and classifies' CPV codes, scoped to Regulation (EC) No 213/2008 8+1 digit codes with Modulo 11 verification. That is precise enough to separate it from siblings like ted_eforms_notice_validator or cig_cup_anac_validator without opening either schema.

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

Usage Guidelines4/5

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

The explicit 'Usage:' line tells the agent to use it on CPV codes in tender documents or to resolve division/group/category hierarchies, which is clear situational guidance. It stops short of naming alternatives or stating when NOT to use it, so it does not reach the 5 bar.

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