Skip to main content
Glama

Dadras — Iranian law (دادرس)

by com.dadrasai
OverviewDiscussionsAdmin

Read one article of an Iranian law

get_law_article
Read-onlyIdempotent

Read the full text of one article of an Iranian statute or regulation, word for word, with its law, the details on its page, a warning when it is marked repealed, and its dadrasai.com link. Use it when the article is known — named by the user or returned by another tool as a slug or link; to find which article covers a subject, use search_iranian_law instead. Dadras's explanatory notes, when present, follow the text under a heading that marks them as not part of the law. When the article is missing, the result says whether the law itself was found and gives its slug and article count for list_law_articles.

Input Schema

NameRequiredDescriptionDefault
lawNoThe law's Persian name, full or short — «قانون مجازات اسلامی», «قانون مدنی». Used with `article`.
slugNoInstead of law and article: an article slug or a dadrasai.com/laws/… link from another tool's result.
articleNoThe article number, in Persian or Latin digits, e.g. «۱۰», «296», «۲۹۶ مکرر». Used with `law`.

Output Schema

NameRequiredDescriptionDefault
textYesThe result, in Persian, as it should be quoted.
linksYesThe dadrasai.com pages the result cites, in order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / article / description
      Previous value: -"Article number, e.g. «۱۰» or «۲۹۶ مکرر»."New value: +"The article number, in Persian or Latin digits, e.g. «۱۰», «296», «۲۹۶ مکرر». Used with `law`."
    • changedInput schema / properties / law / description
      Previous value: -"The law's Persian name, e.g. «قانون مجازات اسلامی»."New value: +"The law's Persian name, full or short — «قانون مجازات اسلامی», «قانون مدنی». Used with `article`."
    • changedInput schema / properties / slug / description
      Previous value: -"An article slug or dadrasai.com/laws/… link instead."New value: +"Instead of law and article: an article slug or a dadrasai.com/laws/… link from another tool's result."
  2. Changed1 schema field changed
    • 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"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: the repealed-article warning, the fact that explanatory notes are labeled as not part of the law, and the missing-article fallback behavior. However, it does not address pagination or size limits for long articles (output schema is not visible here), so it is useful but not exhaustive.

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 core action and return contents, then routing guidance, then edge-case behavior. Dense but each sentence contributes a distinct fact; the middle clause about dadras's explanatory notes is the only part that could be trimmed without loss.

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?

For a read-one-record tool with full schema coverage and an output schema, the description closes the remaining gaps: what to expect when the article is repealed, how explanatory notes are demarcated, and what happens on a miss. Nothing needed to invoke 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 schema already documents law, slug and article, including the law+article pairing and the slug-or-link alternative. The description only repeats that the article may arrive 'as a slug or link' and does not add syntax or format detail (e.g. Persian/Latin digit handling is already in the schema). Baseline 3 applies.

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 ('Read the full text of one article of an Iranian statute or regulation'), and differentiates itself from siblings by naming search_iranian_law and list_law_articles as the tools for adjacent jobs. An agent can tell what it fetches 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?

Explicit selection rule: 'Use it when the article is known — named by the user or returned by another tool as a slug or link,' with the anti-case 'to find which article covers a subject, use search_iranian_law instead.' Both the trigger and the alternative are named.

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 (دادرس) toolsInspect
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