Skip to main content
Glama

Israeli Real Estate and Legal Calculators

court fees

court_fees
Read-only

Israeli court filing fees (agra) for a civil claim by type of proceeding, court and claim amount, under the Courts Regulations (Fees). Runs the official calculator of il-law.co.il.

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": {
      "type": "<type>"
    },
    "name": "court_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the result (default he)
typeYesmoney = monetary claim; reg3 = claim under reg. 3; other = non-monetary; body = bodily injury; sex = sexual offence damages; amend = amended claim; rent = eviction; insolv = insolvency; cc = counterclaim/third party; small = small claims; fam = family court; exec = execution office; appeal = appeal
courtNomag = Magistrates, dist = District
filedNoFiling date (only together with second_half_paid, for linkage of the second half), YYYY-MM-DD
amountNoClaim amount, ILS
second_half_paidNoDate the second half of the fee was paid, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it is an official calculator backed by the Courts Regulations (Fees) and it delegates to il-law.co.il, which tells the agent the figures are authoritative rather than estimated. It stops short of saying what the response contains (a single fee, a breakdown, currency), which matters since there is no output schema.

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, zero filler, with the resource and scope front-loaded and the provenance/legal basis following. Nothing is repeated and nothing needs trimming.

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 six-parameter lookup with no output schema, the description covers what the tool computes and on what authority, but says nothing about the shape of the result (single figure vs. breakdown, currency, whether it reflects linkage or interest). The parameter-level detail is fully carried by the schema, so the remaining gap is the return value.

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% and every parameter, including all three enums, is fully documented in the schema. The description only restates the dimensions the fee depends on (proceeding type, court, claim amount) without adding format, default, or interaction rules beyond what the schema already says.

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 names a specific resource (Israeli court filing fees / agra) and a specific scope (civil claim, by proceeding type, court and amount), plus the governing regulation. It is clearly distinguishable from siblings like court_deadline or purchase_tax, though it never explicitly contrasts itself with any of them.

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 only implied: an agent can infer this is the tool for computing a filing fee for a civil claim. There is no explicit when-to-use statement, no exclusions (e.g. non-civil or criminal matters), and no guidance on when a different tool or a manual check would be preferable.

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.

Resources