Skip to main content
Glama
hebrew-il-mcp

hebrew-il-mcp

by Shtibel1

Israeli VAT rate on a date

israeli_vat_rate

Returns the standard Israeli VAT rate for a given date (YYYY-MM-DD), helping you calculate date-aware VAT accurately.

Instructions

Return the standard Israeli VAT rate in force on a date (YYYY-MM-DD).

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": {
      "date": "<date>"
    },
    "name": "israeli_vat_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/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. 'Return' implies a safe read, but the description never states historical coverage limits, behavior for dates outside the known rate table, or the shape of the returned value (number vs. percentage string). It adds some behavioral context via 'in force on a date' but leaves notable gaps for a tool with zero annotation coverage.

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?

One front-loaded sentence with the verb, resource, and format constraint in that order. Nothing redundant and nothing buried.

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 trivially simple one-parameter lookup this is nearly sufficient, but with no output schema the description should indicate what is returned (a numeric percentage) and whether it covers historical dates. Those omissions are the only real shortfall.

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?

There is a single parameter with 0% schema description coverage, and the description supplies the format (YYYY-MM-DD) plus the key semantic that the date selects which rate applies. The date is a lookup key determining a historical rate, which is meaning beyond the bare string type and regex.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Return') and resource ('standard Israeli VAT rate') with a clear temporal scope ('in force on a date'). It is easily distinguished from the sibling calculate_israeli_vat, though it never explicitly names that sibling as the place to compute VAT on an amount.

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?

The use case (fetch the rate applicable to a given date) is implied clearly enough, but there is no explicit when-to-use or when-not guidance and no pointer to calculate_israeli_vat for actual computation. The agent must infer the boundary itself.

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