Skip to main content
Glama

WritersLogic business agents

checksum

Identifier check digits: IBAN, ISBN, GTIN, VIN, ISIN, LEI and more, in a batch — Validates the format and check digit of up to 100 identifiers per call, for an agent about to put an IBAN, ISBN, GTIN/EAN/UPC, container number, VIN, ISIN, CUSIP, SEDOL, LEI, IMO number, BIC or Luhn number into a payment, order or record. Each item is {kind, value}; with kind omitted the engine proposes candidate kinds and answers unknown if two kinds both validate. Reports the normalized form (lo

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": {
      "items": "<items>"
    },
    "name": "checksum"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose real behavior: the 100-item batch cap, per-item {kind, value} shape, that omitting kind triggers candidate detection, and that ambiguous cases return 'unknown' rather than a guess. It does not state how failures or mixed results are reported per item, and the trailing sentence about the normalized form is cut off, leaving the output contract partly undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core verb and scope, but the identifier list is effectively enumerated twice (once as a headline, once in the use-case clause), inflating the sentence. The text is also truncated mid-word at '(lo', which harms structure.

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 output schema exists, so the description must explain return values, and it only begins to ('Reports the normalized form...') before being cut off. For a validation tool whose whole value is the pass/fail verdict per item, the absence of a complete result description is a meaningful gap, though the input-side behavior is well covered.

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?

Adds meaning beyond the schema: the schema alone says 'Omit to auto-detect', while the description explains the consequence — the engine proposes candidate kinds and answers unknown when two kinds both validate. It also frames the item shape and the batch limit in prose. It does not add anything about the strict flag, which the schema already documents.

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 and resource: validates format and check digits of up to 100 identifiers per batch call, naming the exact identifier families covered. An agent can tell immediately that this is a batch validation tool rather than a generator or parser.

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?

Gives a concrete usage context: use it when about to put an IBAN, ISBN, GTIN/EAN/UPC, container number, VIN, ISIN, CUSIP, SEDOL, LEI, IMO, BIC or Luhn number into a payment, order or record. No when-not guidance or named alternatives, but no sibling in the list plausibly competes, so the context is sufficient.

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