Dadras — Iranian law (دادرس)

Lawyer's power-of-attorney stamp duty (تمبر وکالت)

calculate_stamp_duty

Read-onlyIdempotent

Compute the tax stamp on a lawyer's power of attorney (وکالت‌نامه, article 103 of the Direct Taxes Act) and the fund and Bar shares paid with it, for one stage of one case, civil or criminal. Use it when the question is what the stamp costs; for the lawyer's tariff fee use calculate_lawyer_fee, and for court fees calculate_court_fee. Returns the amounts and their breakdown. Amounts in rial; dates in the Jalali calendar.

Input Schema

Name	Required	Description
`stage`	No	A civil matter is first, appeal, supreme or enforcement. A criminal one is prosecution (دادسرا), first, appeal, order_objection (اعتراض به قرار) or cassation.
`case_kind`	Yes	family covers امور حسبی and the financial claims of a marriage — mehrieh and نفقه are family, not financial. non_judicial is a هیأت such as قانون کار.
`membership`	No	bar is کانون وکلای دادگستری, markaz is مرکز وکلا؛ they owe different shares. bar when not said.
`criminal_band`	No	Which band the gravest charge falls in. court1 is کیفری یک، نظامی یک و انقلاب; court2 is کیفری دو، نظامی دو و اطفال.
`extra_charges`	No	Charges beyond the gravest one, in a criminal case (0–20).
`criminal_final`	No	The criminal first-instance judgment is final (no appeal).
`final_judgment`	No	A financial claim whose judgment cannot be appealed because of its value.
`claim_amount_rial`	No	بهای خواسته, in ریال. Only a financial claim has one.
`contract_fee_rial`	No	The حق‌الوکاله written in the وکالت‌نامه, in ریال. Left out, the stamp is computed on the tariff for that stage, which is also its floor.
`government_client`	No	The client is a ministry, a state company or a شهرداری.
`no_prosecution_stage`	No	A criminal case with no دادسرا stage (it goes straight to court); its share moves to the first instance.

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.

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / criminal_final

Added value: +{
+  "description": "The criminal first-instance judgment is final (no appeal).",
+  "type": "boolean"
+}

changedInput schema / properties / extra_charges / description

Previous value: -"Charges beyond the gravest one, in a criminal case."New value: +"Charges beyond the gravest one, in a criminal case (0–20)."

addedInput schema / properties / final_judgment

Added value: +{
+  "description": "A financial claim whose judgment cannot be appealed because of its value.",
+  "type": "boolean"
+}

addedInput schema / properties / no_prosecution_stage

Added value: +{
+  "description": "A criminal case with no دادسرا stage (it goes straight to court); its share moves to the first instance.",
+  "type": "boolean"
+}

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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context the annotations don't: what is computed (stamp plus fund and Bar shares), the output shape (amounts and their breakdown), and the units/calendar conventions (rial, Jalali). It does not discuss failure modes or rounding assumptions, which is the only gap for a pure calculator.

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?

Three compact sentences, front-loaded with the verb and resource, then routing to siblings, then units. Nothing is redundant and no sentence is filler.

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?

With an output schema present the description needn't spell out return values beyond the brief 'amounts and their breakdown' note, and annotations cover the safety profile. Purpose, alternatives, scope, and unit conventions are all present, leaving nothing an agent needs to call it correctly.

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?

Schema description coverage is 100%, so the baseline is 3 and the heavily annotated enums carry most of the load. The description still adds framing the schema lacks: that the computation is for a single stage of a single case, and that this is a civil-or-criminal distinction, which tells the agent how stage and case_kind interact.

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 resource (compute the tax stamp on a lawyer's power of attorney) and anchors it legally via article 103 of the Direct Taxes Act. It explicitly distinguishes itself from calculate_lawyer_fee and calculate_court_fee, so an agent can disambiguate without reading any schema.

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?

Gives an explicit selection rule ('Use it when the question is what the stamp costs') and names both alternative tools with the condition that routes to each. The 'one stage of one case, civil or criminal' framing also scopes when it applies.

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?