Skip to main content
Glama
mcp-india-stack

mcp-india-stack

calculate_limitation_deadline

Read-onlyIdempotent

Calculate the last date to file a suit, appeal, or application under the Limitation Act using the cause of action, exclusion days, and court closure or reopening dates.

Instructions

Calculate the deadline under the Limitation Act.

Use when computing the last date to file a suit, appeal, or application based on cause of action.

Args: suit_type: Type of suit/appeal/application. cause_of_action_date: Date the cause of action arose (YYYY-MM-DD). exclusion_days: Days excluded under Section 12. court_closed_on_deadline: Whether court is closed on deadline date. court_reopen_date: Date court reopens if closed on deadline.

Returns: Standard envelope with deadline date and limitation period.

Notes: Not legal advice. Consult a qualified advocate.

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": {
      "suit_type": "<suit_type>",
      "cause_of_action_date": "<cause_of_action_date>"
    },
    "name": "calculate_limitation_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
suit_typeYesType of suit/appeal/application to calculate limitation for
exclusion_daysNoDays excluded under Section 12 (e.g. for obtaining copies)
court_reopen_dateNoNext reopening date if court is closed on deadline (Section 4)
cause_of_action_dateYesDate when the cause of action arose (YYYY-MM-DD)
court_closed_on_deadlineNoWhether court is closed on deadline day under Section 4

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.8.0
    • addedInput schema / properties / court_closed_on_deadline
      Added value: +{
      +  "default": false,
      +  "description": "Whether court is closed on deadline day under Section 4",
      +  "title": "Court Closed On Deadline",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / court_reopen_date
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Next reopening date if court is closed on deadline (Section 4)",
      +  "title": "Court Reopen Date"
      +}
    • addedInput schema / properties / exclusion_days
      Added value: +{
      +  "default": 0,
      +  "description": "Days excluded under Section 12 (e.g. for obtaining copies)",
      +  "title": "Exclusion Days",
      +  "type": "integer"
      +}
  2. Addedv0.6.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds some useful context: Sections 12 and 4 drive the exclusion/reopening logic and a 'not legal advice' disclaimer is stated. Beyond that it does not describe edge behavior such as what happens if court_reopen_date is omitted while court_closed_on_deadline is true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in one sentence, then Args/Returns/Notes are cleanly separated. The Args and Returns blocks duplicate what the schema and output schema already provide, which is mild waste but not harmful.

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 deterministic five-parameter calculation with a full schema and an output schema, the description covers trigger, statutory basis, and disclaimer. Nothing essential about invoking it correctly is missing; only unusual input combinations are unspecified.

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 description coverage is 100% and the schema entries are in fact more informative (e.g. the Section 12 example for exclusion_days), so the description's Args block largely restates them. Baseline 3 applies since the schema carries parameter meaning.

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?

States a specific verb and resource ('Calculate the deadline under the Limitation Act') with the statutory basis, which separates it from sibling calculators like calculate_rti_deadline or calculate_court_fee. It does not name those siblings explicitly, so differentiation is inferred from the Act rather than stated.

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?

'Use when computing the last date to file a suit, appeal, or application based on cause of action' gives a clear triggering condition. There is no explicit when-not guidance or pointer to an alternative tool, which keeps it short of a 5.

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

Deploy Server

Other Tools