Skip to main content
Glama

LexGrid European Public Tenders & TED eForms MCP

Universal Common Procurement Vocabulary (CPV) Code Classifier

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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's 'read-only, side-effect free' restates rather than adds. What it does add beyond the annotations is real value: the statutory basis of the calculation and, importantly, the shape of the JSON result (validity flags, cleaned code, hierarchy, descriptions) when no output schema exists.

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, 'Usage:' and 'Returns:' segments front-load the essentials and read efficiently. Minor waste comes from the 'read-only, side-effect free' clause that duplicates fields already in 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?

For a two-parameter stateless validator with no output schema, the definition is nearly sufficient: it names the standard, the digit format, the two usage modes and the return fields. It leaves undefined how keyword input resolves to codes and how the supplementary code interacts with validation, which are the remaining gaps.

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 are already documented in the schema. The description's '8+1 digit codes' phrasing corroborates the input format but adds no new semantics, and the optional supplementaryCode parameter is never mentioned in the description.

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 gives a specific verb pair (validates and classifies) applied to a precise resource: CPV 8+1 digit codes under Regulation (EC) No 213/2008, covering supplies, works and services. The domain specificity (procurement CPV codes plus Modulo 11 check digits) credibly separates it from sibling validators like taric_hs_validator or clp_ufi_code_validator, though it never names an alternative explicitly.

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 'Usage:' line states a clear context — validating CPV codes in tender documents or resolving division, group and category hierarchies. It gives positive guidance but no exclusions, prerequisites, or pointers to the sibling validators the agent might confuse it with.

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