hebrew-il-mcp

Validate Israeli ID / company number

validate_israeli_id

Validates Israeli Teudat Zehut, company, amuta, and Osek Murshe numbers using the official check digit, returning the zero-padded number and detected entity type.

Instructions

Validate an Israeli Teudat Zehut, company (ח.פ), amuta or Osek Murshe number using the official check digit. Returns the zero-padded number and the detected entity kind.

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_israeli_id"
  }
}

Input Schema

Name	Required	Description	Default
`expect`	No		any
`number`	Yes	The number as written, e.g. '12345678-2' or '515555555'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the load and does disclose two useful traits: validation uses the official check digit, and the result includes the zero-padded number plus detected entity kind. It does not say what happens for an invalid number (error vs. a negative result) or whether length/format variations are tolerated, which is the key behavioral unknown for a validator.

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 tight sentences, front-loaded with the action and accepted identifier types, then the return content. No filler, no restatement of the tool name.

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 tool with no output schema, the description usefully covers the return shape and accepted entity kinds. It is incomplete on the two things an agent most needs: the meaning of 'expect' and the failure behavior for an invalid check digit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: 'number' has an example ('12345678-2') but the 'expect' parameter (person/corporate/any) has no description anywhere and is not mentioned in the description text. The description therefore fails to compensate for the undocumented enum, leaving the agent to guess how 'expect' constrains validation.

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 specific verb (validate) plus the exact resource, and enumerates the four Israeli identifier types it handles (Teudat Zehut, ח.פ, amuta, Osek Murshe). The resource is clearly distinct from every sibling (phone, VAT, dates, IBAN), so an agent can route without opening the schema.

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?

Usage is implied rather than stated: the enumerated entity kinds tell the agent this is the tool for checking Israeli identifiers, but there is no explicit when-to-use, no prerequisites, and no mention of how it relates to siblings such as normalize_israeli_phone. Adequate for an obvious single-purpose validator, but no real routing guidance.

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

Deploy Server