Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Luhn check, card validation: check a card or ID number's Luhn checksum

validate_luhn
Read-only

Luhn check: whether a card number or other ID passes the Luhn (mod 10) algorithm used by card numbers, IMEI numbers and many IDs, and compute the check digit to append. Only the format is checked; nothing is looked up. Use to catch typos in card or ID numbers. Example: number=79927398713. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "number": "<number>"
    },
    "name": "validate_luhn"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesDigits, spaces and hyphens allowed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces this ('reads or computes only and changes nothing'). Beyond that it adds genuinely new behavioral facts: cost per call, first 25 free, failed calls free, repeats are not free, and that no external data is queried — information absent from the annotations.

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 core purpose and scope limit are front-loaded, and the example is compact. The closing sentence spends words restating the read-only guarantee already implied by annotations and folds pricing into a semicolon-chained clause, but nothing is outright filler.

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 one-parameter, no-output-schema tool this covers what an agent needs: what is validated, what is not looked up, an accepted input example, and the billing consequence of repeat calls. No important decision-relevant behavior is left unstated.

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% ('Digits, spaces and hyphens allowed'), so the schema already carries the parameter contract. The description adds an example value (79927398713) that is mildly useful, but it leaves the odd schema detail — 'number' also accepting boolean — unexplained, and the 'compute the check digit' capability has no corresponding parameter.

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?

The description names a specific algorithm and resource ('Luhn (mod 10) algorithm', card / IMEI / ID numbers) plus a second capability ('compute the check digit to append'). It also bounds the scope explicitly with 'Only the format is checked; nothing is looked up', which separates it from lookup-style validators such as validate_iban or bic_validate.

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?

It gives a concrete when-to-use rule: 'Use to catch typos in card or ID numbers.' It does not, however, name an alternative tool or state when NOT to use it (e.g. when a real issuer/BIN lookup is needed, or for IBAN/ISBN which have siblings).

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.