Dadras — Iranian law (دادرس)

List the articles of an Iranian law

list_law_articles

Read-onlyIdempotent

List the articles of one Iranian law in order, 50 per page, each with its title and slug, headed by the law's article count and number of pages. Use it to browse a law's structure or to find an article's slug, with a law slug from find_law; then get_law_article reads an article in full. It lists titles, not text, and is not a search: for articles about a subject use search_iranian_law. A page past the end comes back empty and says so.

Input Schema

Name	Required	Description	Default
`page`	No	Which page of 50 articles, from 1; the first result gives the number of pages.
`law_slug`	Yes	The law's slug as find_law returns it.

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.

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / law_slug / description

Previous value: -"From find_law."New value: +"The law's slug as find_law returns it."

changedInput schema / properties / page / description

Previous value: -"Page of 50 articles, from 1."New value: +"Which page of 50 articles, from 1; the first result gives the number of pages."

Changed2 schema fields changedOct 4, 2026

addedInput schema / properties / page / description
```
Added value: +"Page of 50 articles, from 1."
```

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 cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds valuable context beyond annotations: pagination size and ordering, that it returns titles not text, and the past-the-end empty-page behavior. It does not need to explain return values given the 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.

Conciseness5/5

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

Four tight sentences, all front-loaded: what it does, how to use it, what it is not, and an edge case. Every sentence earns its place with no redundancy.

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?

Complete for a read-only listing tool. It covers ordering, page size, return contents, the upstream/downstream tools, the search alternative, and the empty-page edge case, with the output schema handling return values.

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%, so baseline is 3. The description adds meaning: it specifies 50 per page and that the law slug comes from find_law, clarifying the 'law_slug' param's origin and the page numbering context beyond the schema's per-param descriptions.

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 ('List the articles of one Iranian law') and adds scope detail (in order, 50 per page, titles and slugs). It distinguishes itself from siblings like get_law_article (full text) and search_iranian_law (subject search) explicitly.

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 explicit when-to-use cases ('browse a law's structure or find an article's slug'), names the upstream prerequisite (law slug from find_law), names the follow-on tool (get_law_article), and states when NOT to use it ('not a search: for articles about a subject use search_iranian_law'). No inference required.

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?