Skip to main content
Glama

clp_ufi_code_validator

Read-onlyIdempotent

[CLP Annex VIII UFI code checksum validator. Deterministic calculation, read-only, side-effect free]. Validates 16-character Unique Formula Identifiers (UFI) under CLP Annex VIII using the ECHA Base-31 polynomial checksum algorithm for chemical mixture emergency health response. Usage: Pass a UFI code to verify character validity, hyphenation, and mathematical checksum integrity. Returns: JSON object with { ufiCodeFormatted: string, isValidFormat: boolean, isChecksumValid: boolean, payloadCharacteristics: object, pcnNotificationRequirements: 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": {
      "ufiCode": "<ufiCode>"
    },
    "name": "clp_ufi_code_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufiCodeYes16-character UFI code (e.g. V630-1007-A00D-J559)
companyVatNumberNoCompany VAT number used during formulation registration
formulationNumberNoInternal chemical mixture formulation sequence number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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. The description adds useful behavioral context beyond that: deterministic calculation, the specific ECHA Base-31 checksum algorithm, the checks performed, and the returned JSON fields. It does not cover permissions or error cases, but the annotation coverage lowers that burden.

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 description is front-loaded with the tool's identity and algorithm, then gives usage and return structure. It is mostly efficient, though the bracketed read-only/side-effect-free statement partly duplicates annotations and could be tighter.

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 simple read-only validator with full schema coverage and no output schema, the description provides enough context to invoke it correctly and even lists return fields. The main gap is that it does not explain the role of the two optional parameters or how they affect validation.

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 three parameters, including examples and optional-field meaning. The description reinforces the UFI code's validation purpose but adds no material detail about companyVatNumber or formulationNumber, so the baseline of 3 is appropriate.

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 states a specific verb and resource: validates 16-character UFI codes under CLP Annex VIII using the ECHA Base-31 checksum. It is clearly distinct in subject matter from the listed sibling validators, but it does not explicitly name or differentiate itself from any alternative tool.

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?

The 'Usage' sentence explains how to invoke the tool by passing a UFI code, which implies when it should be used. However, it gives no explicit when-to-use guidance versus alternatives, no exclusions, and no sibling routing.

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