Dadras — Iranian law (دادرس)

Late-payment damages (خسارت تأخیر تأدیه)

calculate_late_payment

Read-onlyIdempotent

Compute late-payment damages (خسارت تأخیر تأدیه, article 522 of the Civil Procedure Code) on a debt in rial between the month it fell due and the month it is paid, from the Central Bank's monthly price index. Use it for a money debt, a cheque or a judgment sum; a mehrieh is valued with calculate_mehrieh instead. A month whose index is not published yet uses the latest published one, and the result says so. Returns the damages, their breakdown and the index figures used with their dates. Amounts in rial; dates in the Jalali calendar.

Input Schema

Name	Required	Description
`due_year`	Yes	Jalali year the debt fell due or was demanded.
`due_month`	Yes	Jalali month, 1 for فروردین.
`payment_year`	No	Jalali year of payment; this year when they do not say.
`payment_month`	No	Jalali month of payment, 1 for فروردین.
`principal_rial`	Yes	اصل دین, in ریال.

Output Schema

Name	Required	Description	Default
`text`	Yes	The result, in Persian, as it should be quoted.
`links`	Yes	The dadrasai.com pages the result cites, in order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "links": {
+      "description": "The dadrasai.com pages the result cites, in order.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "text": {
+      "description": "The result, in Persian, as it should be quoted.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text",
+    "links"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds substantive behavior: index publications lag, unpublished months fall back to the latest published index, and the result explicitly flags that fallback. It also declares the return payload (damages, breakdown, index figures with dates) even though an output schema exists.

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?

Front-loaded with the purpose, then legal citation, exclusions, and edge-case behavior, all in three tight sentences with no filler. Slightly dense with parenthetical references but each clause carries rule-bearing content.

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

Completeness5/5

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

Covers what remains after the schema and output schema: whether it applies to this debt type, which sibling handles the excluded case, the index-lag fallback, and the unit/calendar conventions. Nothing needed to call it correctly is missing.

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%, so the baseline is 3. The description adds units and calendar conventions (rial, Jalali) and the fallback for payment_month, but does not go beyond the schema on principal or due-date semantics.

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 (compute) and resource (late-payment damages, خسارت تأخیر تأدیه) and anchors it to the legal basis (article 522 of the Civil Procedure Code). Explicitly distinguishes itself from sibling calculate_mehrieh by use case (mehrieh is valued with that tool instead).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names when to use it (money debt, cheque, judgment sum) and when not to (mehrieh routes to calculate_mehrieh). This is explicit criteria plus an exclusion with a named alternative.

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

All Dadras — Iranian law (دادرس) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?