Skip to main content
Glama

Multi-Identifier Syntax & Checksum Preflight (Free)

syntax_preflight
Read-onlyIdempotent

Free offline mathematical checksum and format preflight across IBAN, BIC, LEI, EU VAT, and UK CRN, with live registry upgrade pointers and a signed receipt.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bic": "NWBKGB2LXXX",
      "lei": "506700GE1G29325QX363",
      "iban": "GB29NWBK60161331926819",
      "company_number": "14043409"
    },
    "name": "syntax_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoOptional 8/11-char SWIFT BIC to test via ISO 9362
leiNoOptional 20-char LEI to test via ISO 17442 MOD 97-10
ibanNoOptional IBAN to test via ISO 7064 MOD 97-10
vat_numberNoOptional EU VAT number
country_codeNoOptional 2-letter EU/XI VAT member-state prefix
company_numberNoOptional UK Companies House number

Output Schema

NameRequiredDescriptionDefault
validNo
checksNo
checked_countNo
existence_guaranteeNo
live_registry_upgradesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered by structured data. The description does add genuinely new context — 'free', 'offline', a 'signed receipt', and upgrade pointers to live registries — but 'offline' sits in mild tension with openWorldHint=true and the nature of the signed receipt is never explained.

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 sentence that front-loads the core value proposition ('Free offline ... preflight'), enumerates scope, and closes with the differentiators. There is no redundant restatement of the title or name.

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 an output schema present, return values need no explanation, and a 100%-covered optional-only schema needs no further parameter prose. The one real gap is that the multi-identifier semantics ('what if I pass several?') and the signed receipt are left unexplained for what is a gateway/preflight tool.

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%, with each parameter documented down to the ISO standard applied and all six being optional. The description adds no parameter-level meaning or guidance on combining identifiers, so the schema carries the full load and the baseline of 3 applies.

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 names a specific verb ('checksum and format preflight') and enumerates exactly which identifier types are covered (IBAN, BIC, LEI, EU VAT, UK CRN), which is well beyond a tautology. It also implicitly separates itself from live-registry siblings via 'offline' and 'live registry upgrade pointers', though it never names an alternative such as iban_check.

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 words 'offline' and 'preflight' combined with 'live registry upgrade pointers' imply this is a cheap first pass before a live lookup, but the routing is left to inference. There is no explicit 'use this instead of X when Y' statement, no prerequisites, and no statement about what happens if no identifiers are supplied.

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.