Skip to main content
Glama
hebrew-il-mcp

hebrew-il-mcp

by Shtibel1

Validate or build an Israeli IBAN

israeli_iban

Validate an Israeli IBAN with MOD 97 check digits, then split it into bank, branch, and account—or build an IBAN from domestic bank details.

Instructions

Validate an Israeli IBAN (MOD 97 check digits) and split it into bank, branch and account, or build the IBAN from domestic bank details (bank code, branch, account number). Pass either iban or bank+branch+account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "israeli_iban"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNoBank code, e.g. '12' for Hapoalim
ibanNoIBAN to validate, e.g. 'IL62 0108 0000 0009 9999 999'
branchNoBranch number
accountNoAccount number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. Disclosing the MOD 97 check and the decomposition output is genuinely useful, but it never states the response shape (valid/invalid flag? parsed object? thrown error?) or whether whitespace/formatting is normalized before checking.

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?

Two sentences, no filler, with the dual behavior and the input-selection rule both front-loaded. Nothing here is redundant or padded.

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?

With no output schema and no annotations, the description should cover the return contract for both modes; it only hints that validation 'splits' the IBAN. An agent still does not know what an invalid IBAN yields or what the build mode returns.

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%, so the schema already documents all four parameters with examples. The description's contribution is the mutually-exclusive pairing constraint (iban XOR bank+branch+account), which the schema does not express — real added value, but limited to that one point.

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 two specific verbs (validate/split, build) on a specific resource (Israeli IBAN), plus the MOD 97 check it performs. The tool is unambiguously distinguishable from the Hebrew/phone/VAT siblings.

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?

"Pass either iban or bank+branch+account" gives explicit mode selection, which is exactly the decision an agent needs to make. It stops short of saying what happens when neither set is supplied or when validation fails, so no true when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.