Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

validate_identifier

Read-onlyIdempotent

utilpeek: check the format and check digits of an identifier. For a VIN's vehicle use decode_vin; for phone numbers use parse_phone_number. Returns valid, reason (invalid_checksum, invalid_length, invalid_format, ... when not valid), compact, formatted and a kind-specific detail (an IBAN's country and bank code, an ISBN's ISBN-10/13 forms, ...). An invalid identifier is a normal answer (charged); a malformed request is a 422 (not charged). Checks format and check digits only, offline (python-stdnum): a valid result does not mean the identifier exists or is registered (no registry, bank or VIES call). Payment card numbers are not accepted, not even under luhn. The submitted value is processed in memory only, never logged or stored. Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/iban-validation-api.html

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": {
      "kind": "<kind>",
      "value": "<value>"
    },
    "name": "validate_identifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesIdentifier kind: iban, bic, vat (EU, format only, no VIES), isbn, issn, ean, isin, lei, imo, luhn (generic mod-10), or a national format (au_abn, br_cnpj, br_cpf, ca_bn, ch_uid, de_idnr, es_nif, fr_siren, fr_siret, gb_vat, in_pan, mx_rfc, nl_bsn, us_ein). No payment card numbers.
valueYesThe identifier (1-64 printable ASCII characters).

Output Schema

NameRequiredDescriptionDefault
kindNo
noteNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
labelNo
validNo
detailNo
reasonNo
sourceNo
compactNo
formattedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / value / title
      Removed value: -"Value"
    • removedInput schema / title
      Removed value: -"validate_identifierArguments"
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "library": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "compact": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "detail": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "formatted": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "kind": {
      +      "enum": [
      +        "iban",
      +        "bic",
      +        "vat",
      +        "isbn",
      +        "issn",
      +        "ean",
      +        "isin",
      +        "lei",
      +        "imo",
      +        "luhn",
      +        "au_abn",
      +        "br_cnpj",
      +        "br_cpf",
      +        "ca_bn",
      +        "ch_uid",
      +        "de_idnr",
      +        "es_nif",
      +        "fr_siren",
      +        "fr_siret",
      +        "gb_vat",
      +        "in_pan",
      +        "mx_rfc",
      +        "nl_bsn",
      +        "us_ein",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "label": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "properties": {
      +        "library": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "url": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "valid": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: offline python-stdnum validation, no registry/bank/VIES call, no proof of existence, in-memory processing with no logging, sub-0.1s latency, price and free-quota. The only mild deduction is that cost mechanics and docs URL crowd what is otherwise behavioral disclosure, and return-shape detail is partly duplicated with the output schema.

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?

Front-loaded with purpose and sibling routing, then constraints, then returns and commercial terms — a sensible ordering with no filler sentences. It is a dense block rather than scannable structure, and pricing/docs/latency sit in the same run-on paragraph, which slightly hurts readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter validator it covers the decision-critical facts: what is and isn't checked, what an invalid result means, which kinds are accepted, exclusivity rules, and the shape of the response and its reason codes. Even though an output schema exists, the inline summary of valid/reason/compact/formatted/detail is consistent and not contradictory.

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% and the enum already documents every kind, including "vat (EU, format only, no VIES)" and "luhn (generic mod-10)", so the description largely restates structured content. It adds only the negative constraint on card numbers, which is also in the enum description, so baseline 3 applies.

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 concrete verb and resource ("check the format and check digits of an identifier") and immediately narrows scope to format/checksum rather than existence. It also names the two sibling tools that own adjacent identifier types, so an agent can distinguish it from decode_vin and parse_phone_number without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes VINs to decode_vin and phone numbers to parse_phone_number, and explicitly excludes payment card numbers "not even under `luhn`". It also sets expectations that an invalid identifier is a normal charged answer while a malformed request is a 422, which resolves the main decision ambiguity.

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.