Skip to main content
Glama

Israeli Real Estate and Legal Calculators

court deadline

court_deadline
Read-only

Last day for filing a pleading, motion or appeal in Israeli civil courts under the Civil Procedure Regulations 2018: counts from service, excludes court recess (Sukkot, Passover, summer), moves a last day falling on Friday, Saturday or a holiday, and applies reg. 161 for late electronic service. Runs the official deadlines 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": {
      "act": "<act>",
      "service_date": "<service_date>"
    },
    "name": "court_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
actYesdefense = statement of defence; defmed = defence in a medical malpractice claim; deffast = defence in expedited procedure; defevict = defence in an eviction claim; reply = reply to defence; third = third-party notice; thirdfast = third-party notice in expedited procedure; amend = amended pleading; motion = response to a motion; reqlist = response to request for documents/interrogatories; setaside = motion to set aside a judgment; appeal = appeal; crossapp = cross-appeal; appresp = response/reply in appeal; medcounter = counter expert opinion (medical)
langNoLanguage of the result (default he)
service_dateYesDate, YYYY-MM-DD
service_timeNoHH:MM, for electronic or fax service (optional)
service_methodNoelec = electronic (Net Hamishpat/e-mail), mail = registered mail, personal = personal delivery, fax, court = given in court

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight and delivers: the counting start point (service), recess exclusion with named holidays, weekend/holiday rollover of the last day, and reg. 161 handling for late electronic service. The one thing an agent might notice is the mild tension between 'runs the official deadlines calculator of il-law.co.il' and openWorldHint=false, though a fixed hosted calculator is plausibly closed-world; no contradiction is claimed.

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 dense sentence that front-loads the purpose and then enumerates the computation rules in the order an agent needs them. Every clause — reg. 161, recess exclusions, rollover — carries distinct information; nothing is padding.

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?

With no output schema, the agent is left to infer the return shape (presumably a computed date or schedule), which is the main unaddressed gap. Everything else — domain, legal basis, rule set, and all input enums via the schema — is covered for a 5-parameter calculator.

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% with fully documented enums, including per-value glosses for every act code and service method. The description adds rule context (counting from service, reg. 161 for late electronic service) that hints at why service_date/service_method/service_time interact, but it does not explain individual parameter effects beyond the schema.

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 and output ('Last day for filing a pleading, motion or appeal') plus the exact legal domain ('Israeli civil courts under the Civil Procedure Regulations 2018'). No sibling tool covers deadlines — the rest are fees, taxes, linkage, warranty — so the scope is unambiguous without naming an alternative.

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?

The use case is clear from 'last day for filing ... in Israeli civil courts', which implicitly scopes out criminal/administrative matters and non-filing calculations. There is no explicit when-not guidance or named alternative, but the sibling set contains nothing overlapping, so the practical risk of misrouting is low.

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