Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_eu_vat_iban

Read-onlyIdempotent

EU VAT & IBAN/BIC Checksum Validator API: Validate IBAN MOD-97 checksums, BIC/SWIFT codes, and EU27 VAT formats offline. (Endpoint: POST /v1/eu-vat-iban/iban)

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": {
      "iban": "<iban>"
    },
    "name": "tinplate_eu_vat_iban"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoOptional BIC/SWIFT code (8 or 11 characters) to validate and cross-check country.
ibanYesIBAN to validate (spaces allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed9 schema fields changed
    • changedInput schema / properties / bic / description
      Previous value: -"Parameter 'bic' (e.g. \"COBADEFFXXX\")"New value: +"Optional BIC/SWIFT code (8 or 11 characters) to validate and cross-check country."
    • addedInput schema / properties / bic / example
      Added value: +"COBADEFFXXX"
    • addedInput schema / properties / bic / maxLength
      Added value: +16
    • addedInput schema / properties / bic / minLength
      Added value: +4
    • changedInput schema / properties / iban / description
      Previous value: -"Parameter 'iban' (e.g. \"DE89 3704 0044 0532 0130 00\")"New value: +"IBAN to validate (spaces allowed)."
    • addedInput schema / properties / iban / example
      Added value: +"DE89 3704 0044 0532 0130 00"
    • addedInput schema / properties / iban / maxLength
      Added value: +64
    • addedInput schema / properties / iban / minLength
      Added value: +5
    • changedInput schema / required
      Previous value: -[
      -  "iban",
      -  "bic"
      -]New value: +[
      +  "iban"
      +]
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and mutation behavior need little restating. The description contributes the meaningful detail that validation is offline/checksum-based and names the endpoint, but it does not say what an invalid checksum yields (error versus a result flag) or what the response contains. That is a modest addition over annotations, hence a 3 rather than lower.

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?

Two compact clauses with the verb and value proposition front-loaded, and the endpoint appended where it is useful. The only waste is the VAT wording, which adds length without adding applicable scope.

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?

For a two-parameter pure-validation tool this is close to sufficient, and no output schema exists so return values arguably need not be spelled out. Still, the description overclaims VAT coverage relative to its schema and never indicates whether failures are errors or result fields, leaving an agent guessing at the contract.

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 coverage is 100%; the schema already explains that iban allows spaces and that bic is an optional 8/11-character cross-check. The description adds no syntax, format, or cross-check semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a specific verb (validate) and resources (IBAN MOD-97, BIC/SWIFT, EU27 VAT), which is more than a restated name. But the scope claim is inconsistent with the tool itself: the endpoint cited is POST /v1/eu-vat-iban/iban and the schema accepts only iban and bic, so advertising VAT-format validation muddies what the tool actually does and blurs the line with the sibling tinplate_eu_vat_iban_vat.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no pointer to the VAT-specific sibling even though the description raises VAT as a concern. The agent must infer from the endpoint line that this is the IBAN/BIC entry point.

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