Skip to main content
Glama
hebrew-il-mcp

hebrew-il-mcp

by Shtibel1

Calculate Israeli VAT (מע"מ)

calculate_israeli_vat

Add VAT to a net amount or extract VAT from a VAT-inclusive amount using the Israeli rate in force on a specified date, defaulting to today.

Instructions

Add VAT to a net amount or split a VAT-inclusive amount, using the Israeli VAT rate that was in force on the given date (defaults to today).

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": {
      "amount": "<amount>",
      "includesVat": "<includesVat>"
    },
    "name": "calculate_israeli_vat"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoTransaction date, YYYY-MM-DD
amountYes
includesVatYestrue if the amount already includes VAT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a key behavioral trait: the rate is the one historically in force on the given date, not the current rate. However, it says nothing about rounding/precision, currency, or what happens for future dates, which are meaningful gaps for a calculation tool.

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?

A single front-loaded sentence that states the two operations first and the date-rate nuance second. Nothing is redundant.

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

Completeness4/5

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

For a simple three-parameter computation with no output schema, the description covers what an agent needs to select and invoke it. It would be stronger if it indicated the returned breakdown (net / VAT / gross), since no output schema documents the result shape.

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

Parameters4/5

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

Schema coverage is 67% (the undocumented `amount` is self-explanatory from its name and minimum:0 constraint). The description adds real meaning beyond the schema: `date` selects the historically applicable rate and defaults to today, and `includesVat` selects between the add-VAT and split-VAT modes.

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 verb+resource pair ('Add VAT to a net amount or split a VAT-inclusive amount'), including both directions of the calculation. It implicitly distinguishes itself from the `israeli_vat_rate` sibling by framing itself as an amount calculator rather than a rate lookup.

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 by the operation described, but there is no explicit guidance on when to prefer this over `israeli_vat_rate` (e.g., 'use israeli_vat_rate if you only need the percentage'). The default-to-today behavior is stated, which helps, but no exclusions or alternatives are named.

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