Dadras — Iranian law (دادرس)

Explain an Iranian legal term (واژه‌نامهٔ حقوقی)

explain_legal_term

Read-onlyIdempotent

Explain what a Persian legal term means — «مهرالمثل», «اعسار», «قیم», «سرقفلی» — from Dadras's legal glossary: up to three distinct definitions, each with the article it explains and that article's dadrasai.com link. Use it when the question is what a legal word means; for the rules that apply to it, use search_iranian_law. When the whole phrase has no entry, its most specific word is looked up and the result names the word defined. The definitions are Dadras's explanatory notes, not statutory text.

Input Schema

Name	Required	Description	Default
`term`	Yes	The term in Persian, one or two words, e.g. «مهرالمثل» or «خیار غبن».

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 5, 2026

changedInput schema / properties / term / description

Previous value: -"The term in Persian, e.g. «مهرالمثل»."New value: +"The term in Persian, one or two words, e.g. «مهرالمثل» or «خیار غبن»."

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

Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world behavior, yet the description adds substantive traits: up to three distinct definitions with their source article and link, a fallback rule when the whole phrase has no entry (most specific word is looked up and named in the result), and a caveat that definitions are explanatory notes rather than statutory text.

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-loads the core purpose and examples, then usage routing, then the fallback caveat. Every sentence carries information, though the definition of "distinct definitions" and the source caveat could be tightened slightly.

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, return formatting need not be described. The description still covers source, result shape, fallback behavior, and the sibling alternative, leaving nothing an agent needs in order to call this 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 coverage is 100% and the single parameter is fully documented, so baseline is 3. The description goes further by explaining multi-word phrase handling (the most specific word is resolved and named in the result), which tells the agent how an ambiguous input is interpreted.

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 (explain) and resource (a Persian legal term), names the source (Dadras's legal glossary), and gives concrete example terms. An agent can distinguish it from the calculate_* and law-lookup siblings without opening the 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?

Explicitly states the triggering condition ("Use it when the question is what a legal word means") and names the alternative with its own condition ("for the rules that apply to it, use search_iranian_law"). This is exactly the when/when-not/alternative pattern.

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?